Image
EAN-139780747589716   EAN-13 barcode 9780747589716
Product NameJess Makes a Promise: No. 10: Mermaid SOS
CategoryBook / Magazine / Publication
Short DescriptionPaperback
Amazon.comA Buy on Amazon ~ 0747589712
SKUGRP30646391
Price New63.43 US Dollars    (curriencies)
Price Used4.99 US Dollars    (curriencies)
Width0.28 inches    (convert)
Height7.72 inches    (convert)
Length5.2 inches    (convert)
Weight2.56 ounces    (convert)
AuthorGillian Shields
Page Count96
BindingPaperback
Published05/07/2007
Long DescriptionRiding on the back of Monty, the Whale Express, to the Beachcomber Islands, the mermaids come under attack from a whaling boat. Jess devises an ingenious plan to outwit the whalers as well as helping the smaller sealife at the bottom of the ocean as well. Although Jess puts herself into a lot of danger to save her friends, her actions also lead the brave mermaids towards the next Snow Diamond.
Similar Items9781599902555: Scarlett's New Friend (Mermaid S.O.S.)
9781599902081: Misty to the Rescue: Mermaid S.O.S. #1
9780747587668: Ellie And The Secret Potion: No. 2: Mermaid Sos
9781599903361: Amber's First Clue (Mermaid S.O.S.)
9780545112789: Katie And The Snow Babies: Mermaid S.O.S. #8
9780747587705: Lucy and the Magic Crystal: No. 6: Mermaid SOS
9781599902142: Holly Takes a Risk (Mermaid S.O.S.)
9780747589754: Katie And The Snow Babies: No. 8: Mermaid Sos
9780747589709: Megan and the Night Diamond: No. 9: Mermaid SOS
9780747589730: Poppy's Last Chance: No. 12: Mermaid Sos
Created11-16-2012 1:17:41pm
Modified09-03-2017 12:10:48pm
MD57c355b05f6e66aa3c417c63df22596ab
SHA256e63aa9a23f8b8946f1208621e7e29ca0c24c8e75eca502f04809d68ec9cb3fe9
Search Googleby EAN or by Title
Query Time0.0221391

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