Image
EAN-130786936292992   EAN-13 barcode 0786936292992
UPC-A786936292992   UPC-A barcode 786936292992
Product NamePirates of the Caribbean At World's End
LanguageEnglish
CategoryElectronics / Photography: A/V Media: Movie / TV
Short DescriptionDVD
Amazon.comA Buy on Amazon ~ B000U7WV1Y
SKU20110702131369
Price New2.98 US Dollars    (curriencies)
Price Used0.01 US Dollars    (curriencies)
Long Description###############################################################################################################################################################################################################################################################
Similar Items8717418309596: Pirates of the Caribbean: On Stranger Tides (Blu-ray + DVD) [Region Free]
8717418157319: National Treasure: Book of Secrets
8717418130091: Pirates of The Caribbean - Dead Man's Chest [Import anglais]
8717418124878: Pirates of the Caribbean [Blu-ray]
8717418124861: Pirates of the Caribbean [Blu-ray]
8717418090500: Pirates of The Caribbean - The Curse of The Black Pearl [Import anglais]
8717418087050: Fluch Der Karibik
5039036071703: Dawn of the Planet of the Apes / Rise of the Planet of the Apes [Double Pack] [DVD]
5017188816212: Pirates of the Caribbean: The Curse of the Black Pearl
0786936224306: Pirates of the Caribbean The Curse of the Black Pearl
0085393165529: Terminator 3: Rise of the Machines
0031398283751: Hunger Games Collection
Created05-22-2010
Modified10-12-2017 7:57:15pm
MD5f7c0bf6274886fc36b25ffd2a3cce64c
SHA2564810f6f420556830f789bbb3c25746b1b38ded404e4cf471502fff1f98d4894c
Search Googleby EAN or by Title
Query Time0.0245411

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 sample_ean_data.zip 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.

LOAD DATA LOCAL
    INFILE '~/sample_ean_data/sample_ean_product.csv' 
    INTO TABLE ean_product
    FIELDS TERMINATED BY ',' ENCLOSED BY '"' ESCAPED BY '\\'
    LINES TERMINATED BY '\r\n'
    IGNORE 1 LINES;

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

SELECT * FROM EAN_PRODUCT;

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.

Close

Search

Close

Share