Image
EAN-13	9780756405380
Product Name	Crime Spells
Category	Book / Magazine / Publication
Short Description	Height:6.61 inches / Length:4.09 inches / Weight:0.35 pounds / Width:1.3 inches
Amazon.com	Buy on Amazon ~ 0756405386
SKU	I9780756405380
Price New	1.37 US Dollars    (curriencies)
Price Used	2.25 US Dollars    (curriencies)
Width	0.85 inches    (convert)
Height	6.7 inches    (convert)
Length	4.2 inches    (convert)
Weight	5.6 ounces    (convert)
Page Count	320
Binding	Mass Market Paperback
Published	02/03/2009
Long Description	Sixteen original stories about magic-fueled crimes and those who investigate them When magic is used for criminal purposes, all sorts of ethical and logistical questions arise beyond the realm of everyday law and order. Now, sixteen top tale-tellers offer fascinating new stories of those who commit magic crimes, those who investigate them, and those who prosecute them. From a young woman who uses out-of-body excursions to research paranormal crimes to a bookie who?s been paying for hex protection against magical interference to an artist who does divination through his sketched visions which may lead to a murderer?s undoing, here are powerful tales of magical crimes and punishments.
Similar Items	9781435126886: Love Is Strange: An Anthology Of Paranormal Romance Stories 9780756406509: Love And Rockets 9780756405106: Enchantment Place 9780756404727: Something Magic This Way Comes 9780756403799: The Magic Toybox
Created	11-22-2012 12:19:43pm
Modified	05-27-2017 8:33:12am
MD5	ef7938b7327320f03d070aeaa9917d1b
SHA256	5fec98536af4b7a4a895e3d2deab70bb61482b8cf515d466aa3a7bcad0889c33
Search Google	by EAN or by Title
Query Time	0.0065980

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.