Image
EAN-130000000004664   EAN-13 barcode 0000000004664
UPC-A000000004664   UPC-A barcode 000000004664
UPC-E00046604   UPC-E barcode 00046604
Product NameFallkniven Knives FN13K 11 1/8" Fixed Blade.
CategoryOutdoor
Amazon.comA Buy on Amazon ~ B0006PT5PA
SKU36108322
ModelA1BLZ
Price New225.55 US Dollars    (curriencies)
Weight16 ounces    (convert)
BindingAudio CD
Features
  • Blade Length: 6.33 inches
  • Blade Material: Stainless Steel (VG-10)
  • Sheath Material: Zytel
  • Blade Edge: Plain
  • Point: Drop Point
Long DescriptionFallkniven A1 Fixed Blade Survival Knife with Black Blade and Zytel Sheath: Model FN-13K. 11 1/8" overall. 6 3/8" black Teflon coated VG-10 stainless modified spear point blade. Black checkered Thermorun elastomer handle with visible tang end and lanyard hole. Black Zytel belt sheath included. Made in Japan.
Created04-14-2012 11:07:55pm
Modified09-05-2017 3:00:20pm
MD5d18bc81011d5aaef5c223336485022ef
SHA2562c2a1c90749d871c11a576ce53aa6bfb2776a864d43f44ac28c6d816384a46ed
Search Googleby EAN or by Title
Query Time0.0058498

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