|Product Name||Two Faces of January|
|Category||Electronics / Photography: A/V Media: Movie / TV|
|Amazon.com||Buy on Amazon ~ B00OLIIEZK|
|Price New||2.99 US Dollars (curriencies)|
|Price Used||1.97 US Dollars (curriencies)|
|Rating||PG-13 - Parents Strongly Cautioned|
|Trailer||Watch The Trailer|
|Run Time||96 minutes|
|Cast||Oscar Isaac, Viggo Mortensen, Kirsten Dunst, Daisy Bevan|
|Run Time||97 minutes|
|Width||5.25 inches (convert)|
|Height||0.5 inches (convert)|
|Length||7.25 inches (convert)|
|Weight||20 hundredths pounds (convert)|
|Format||Multiple Formats, Closed-captioned, Color, Dolby, DTS Surround Sound, Dubbed, Subtitled, Widescreen, NTSC|
|Run Time||97 minutes|
|Features||Factory sealed DVD|
|Long Description||1962. A glamorous American couple, the charismatic Chester MacFarland (Mortensen) and his alluring younger wife Colette (Dunst), arrive in Athens by boat via the Corinth Canal. While sightseeing at the Acropolis they encounter Rydal (Isaac), a young, Greek-speaking American who is working as a tour guide, scamming tourists on the side. Drawn to Colette's beauty and impressed by Chester's wealth and sophistication, Rydal gladly accepts their invitation to dinner. However, all is not as it seems with the MacFarlands and Chester's affable exterior hides darker secrets. When Rydal visits the couple at their exclusive hotel, Chester presses him to help move the body of a seemingly unconscious man who he claims attacked him. In the moment, Rydal agrees but as events take a more sinister turn he finds himself compromised and unable to pull himself free. His increasing infatuation with the vulnerable and responsive Colette gives rise to Chester's jealousy and paranoia, leading to a tense and dangerous battle of wits between the two men.|
|Similar Items||9780792851561: The Indian Runner|
0883929571864: Blade Runner 2049
0876964008013: White Bird in a Blizzard
0794043100956: A History of Violence
0738329201579: Far From Men
0043396395039: A Dangerous Method
0031398216520: A Most Violent Year
0027616921413: Indian Runner
0025192358913: Captain Fantastic
0024543416265: Three Billboards Outside Ebbing, Missouri
0014381901627: American Yakuza
|Search Google||by EAN or by Title|
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
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
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.