Image
EAN-130000007480447   EAN-13 barcode 0000007480447
UPC-A000007480447   UPC-A barcode 000007480447
Product NameCaza Trail Hazelnut 48 K-Cups
CategoryFood
Amazon.comA Buy on Amazon ~ B00CL0T5N0
Long DescriptionThe word "caza" (Spanish for the "hunt") expresses the thrill of the hunt - and CAZA TRAIL is the prize that we're thrilled to share with you, following our worldwide search for a rich, capitivating bre - the coffee lover's ultimate prey. We pursue the most delicious varieties and flavors to ensure that for every mood and any time of day, the hunt for a rich, captivating cup can always be satisfied. With each one, you'll taste the care and quality that goes into Caza TrailTM, and the unique essences captured in every sip. Treasure them one by one and enjoy the journey.
Created05-20-2010
Modified06-29-2020 4:12:31am
MD57abbfa28094b357c99a1b7ae52f2dad8
SHA2569336e4d61526f6c13f86c2718e15e92db3dd7eb0bad8743fc286443ffaaa977b
Search Googleby EAN or by Title
Query Time0.0051808

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

Close

Dialog