| Image |  |
| EAN-13 | 9780786293889  |
| Product Name | White Cargo |
| Category | Book / Magazine / Publication |
| Short Description | Hardcover |
| Amazon.com |  Buy on Amazon ~ 0786293888 |
| SKU | !~@0RDCXU`15@3SEMQ_2007_UNK2 |
| Price New | 103.82 US Dollars (curriencies) |
| Price Used | 7.15 US Dollars (curriencies) |
| Width | 5.86 inches (convert) |
| Height | 1.16 inches (convert) |
| Length | 8.5 inches (convert) |
| Author | Stuart Woods |
| Page Count | 523 |
| Binding | Hardcover |
| Published | 04/01/2007 |
| Long Description | A multi-millionaire takes his wife and daughter on an idyllic yacht cruise to the South Pacific, but in Colombia one moment of savage brutality loses him everything he loves. Driven by thin hope and desperation, he begins a murderous hunt which will lead him to the country's most notorious drugs baron. Stuart Woods has also written "Under the Lake" and "Deep Lie". |
| Similar Items | 9780712648936: Doing Hard Time (A Stone Barrington Novel) 9780689854248: Doing Hard Time (A Stone Barrington Novel) 9780548419601: Doing Hard Time (A Stone Barrington Novel) 9780399164149: Doing Hard Time (A Stone Barrington Novel) 9780393042719: Doing Hard Time (A Stone Barrington Novel) 9780312222390: Doing Hard Time (A Stone Barrington Novel) 9780399159879: Unintended Consequences (Stone Barrington, Book 26) (A Stone Barrington Novel) 9780385751544: Unintended Consequences (Stone Barrington, Book 26) (A Stone Barrington Novel) 9780393022728: Deep Lie 9780060177768: Heat View 16 more similar items |
| Created | 04-22-2012 1:05:00am |
| Modified | 04-27-2017 7:40:18pm |
| MD5 | 7b76785ee3cb9dee2ca5613004875b7c |
| SHA256 | cd4118c9ab968fbf46ee3c566ede5582976f443e51157989edddf71ce02bf8e8 |
| Search Google | by EAN or by Title |
| Query Time | 0.0267229 |
An article of interest
Making use of the tools we offer
Importing our data into your MySQL database
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.