Image
EAN-130010164156420   EAN-13 barcode 0010164156420
UPC-A010164156420   UPC-A barcode 010164156420
Product NameRed Alert 2 Original Soundtrack
CategoryElectronics / Photography: A/V Media: Music
Short Description2 oz
Amazon.comA Buy on Amazon ~ B003NUIX76
SKUJUL11D04-72373
Price Used49.95 US Dollars    (curriencies)
AuthorFrank Klepacki
BindingAudio Cd
Published01/17/2014
Long DescriptionThis rare official soundtrack from the popular video game Command & Conquer: Red Alert 2 was only available for a very short period of time and is almost impossible to find now. Featuring over an hour of original music by veteran series composer Frank Klepacki -- including the infamous Hell March 2 -- this pulse-pounding score is sure to be a hit with any fan on the Command & Conquer series!
Created07-01-2006
Modified10-04-2017 4:06:28pm
MD5442963051573e6582f994901f1dbf4aa
SHA2564a3fa9f5e2fb395710164a41a64c8bcab4d0772f4ad963a1be0798f84ba534de
Search Googleby EAN or by Title
Query Time0.0042982

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