Image
EAN-139781560774464   EAN-13 barcode 9781560774464
Product NameRockhounding Utah (A Falcon Guide)
CategoryBook / Magazine / Publication
Short DescriptionHardcover
Amazon.comA Buy on Amazon ~ 1560774460
Price Used28.39 US Dollars    (curriencies)
AuthorWilliam A. Kappele
Page Count180
BindingPaperback
Published06/01/1996
Long DescriptionEighty-six sites.
Similar Items0051442100544: Grit Pack For #130 Or #140
0034139626213: Estwing E3-22p 22-Ounce Rock Pick
9780762744497: Rockhounding Arizona: A Guide To 75 Of The State's Best Rockhounding Sites (Rockhounding Series)
9780878422289: Roadside Geology Of Utah (Roadside Geology Series)
9780762782161: Rockhounding Utah: A Guide To The State's Best Rockhounding Sites (Rockhounding Series)
9781889786377: Gem Trails Of Utah
9781560444459: Rockhounding Wyoming (A Falcon Guide)
9780762771424: Rockhounding Nevada: A Guide To The State's Best Rockhounding Sites (Rockhounding Series)
9780762748129: Rockhounding Idaho: A Guide To 99 Of The State's Best Rockhounding Sites (Rockhounding Series)
9780762728503: Rockhounding Colorado (Rockhounding Series)
Created04-23-2012 1:05:00am
Modified05-01-2020 5:24:03pm
MD59aa86aa181c6ce1087df919ba43ca6e1
SHA256c98068d80908a51b2472a72501a22f5d8d760f203af81cfdba661d446fd8ca87
Search Googleby EAN or by Title
Query Time0.0326071

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