Image
EAN-139780531071366   EAN-13 barcode 9780531071366
Product NameNothing Ever Happens On 90th Street
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionPaperback
Amazon.comA Buy on Amazon ~ 0531071367
SKU400069143084523971835319
Price New2.47 US Dollars    (curriencies)
Price Used1.19 US Dollars    (curriencies)
Width8.75 inches    (convert)
Height10.75 inches    (convert)
Length0.25 inches    (convert)
Weight4 ounces    (convert)
AuthorRoni Schotter
Page Count32
BindingPaperback
Published09/01/1999
FeaturesGreat product!
Long DescriptionWhen Eva sits on her stoop trying to complete a school assignment by writing about what happens in her neighborhood, she gets a great deal of advice and action.
Similar Items9780395848265: Twilight Comes Twice
9780395811368: Home Place
9780152162412: Grody's Not So Golden Rules
9781416909057: Amelia's Notebook
9780871922939: Through The Cracks
9780804568296: Peppe The Lamplighter
9780064437530: The Secret Knowledge Of Grown-Ups
9780399250910: Back Of The Bus
9781564028594: The Private Notebook Of Katie Roberts, Age 11
9780021794898: Home Place
View 126 more similar items
Created07-21-2012 1:05:00am
Modified09-29-2017 8:09:42am
MD531c1d6cfe47a29c38f911c4e2cf4965d
SHA256dd8344c664b032107da740ffb25b7bcf25c14a5872e89bb691eee7af4e0aa7c4
Search Googleby EAN or by Title
Query Time0.0227671

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