EAN-130886470659791   EAN-13 barcode 0886470659791
UPC-A886470659791   UPC-A barcode 886470659791
Product NameLove, Lies and Murder
CategoryElectronics / Photography: A/V Media: Movie / TV
Amazon.comA Buy on Amazon ~ B008BN58EG
Price New15.48 US Dollars    (curriencies)
Price Used17.08 US Dollars    (curriencies)
Long DescriptionA chilling mini-series based on the 1985 true story of David A. Brown, a computer whiz, who orchestrated his wife’s murder with the help of two trusting…but totally manipulated…teenage girls. Brown (played by Clancy Brown) masterminded this bizarre murder plot by luring his teenage daughter (Moira Kelly), and 17-year-old sister-in-law (Sheryl Lee) into the cold-blooded shooting of his wife. As the lies are peeled away, layer after layer, his sinister web of treachery, deceit, and manipulation is finally shattered in a hailstorm of staggering revelations. The gripping tale of “an almost perfect murder” – an unflinching portrait of a terrifying killer – LOVE, LIES AND MURDER is an unforgettable look at one of the most shocking crimes of the last three decades. For the first time on DVD, LOVE, LIES, AND MURDER proves once and for all that fact is truly stranger than fiction. This product is manufactured on demand using DVD-R recordable media.'s standard return policy will apply. This product is expected to play back in DVD Video "play only" devices, and may not play in other DVD devices, including recorders and PC drives.
Similar Items9781404931268: Murder in Greenwich
9780783120195: Positively True Adventures of the Alleged Texas Cheerleader-Murdering Mom
9780766212190: Love, Murder and Deceit
0779836185990: Killing Secret
0779836177698: Swearing Allegiance
0084296402991: Too Young to Die?
Created03-14-2013 1:50:12am
Modified04-30-2020 9:01:25am
Search Googleby EAN or by Title
Query Time0.0154929

Article of interest

Here we will demonstrate the most basic example of importing the CSV data files that we produce on this site into your MySQL database.

For information about various databases you can use and how to import CSV files into them, please view the overview article "Importing CSV data into your database".

For this example, we are going to import the product data CSV file out of the but this same process will work on the full data download file. We will also be executing the commands in the MySQL Workbench but you can also use the command line tool with the same commands if you like.

First, start by creating a blank table. Use the table layout described in the read_me file for the most up-to-date table layout. It is suggested that you not use any indexing at this point. You can add indexes later. It is most likely that you will have your own tables where you want to store your data so importing the CSV files can be done into temporary tables and then later copied over to your tables. Leaving off the indexes and constraints on these import tables reduces the risk of import errors. Here is an example:

create table ean_product
    EAN13             varchar(13),
    UPCA              varchar(12),
    UPCE              varchar(8),
    SKU               varchar(200),
    PriceNew          numeric(15,2),
    PriceUsed         numeric(15,2),
    PriceDate         date,
    company           varchar(13),
    product           varchar(100),
    description       varchar(100),
    category          int,
    url               varchar(500),
    created           datetime,
    modified          datetime

Next we perform the import using the LOAD DATA INFILE command. The path to the file depends on where you saved the data and which operating system you are on. For Windows users you might find your file on the C: drive and Linux users may find your date in your home (~) folder. This example shows a Linux import. Only the path would be different between the operating systems.

    INFILE '~/sample_ean_data/sample_ean_product.csv' 
    INTO TABLE ean_product

Finally, lets look at the data that we just imported.


You may have seen some warnings after the import command. If you are concerned about these warnings, examine the data. It could be that some data has grown beyond the size specified in the read_me file. If you are worried, make the fields larger and try the process again after deleting all of the data out of the table.