StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12634652
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-09-28T06:23:56.463
FavoriteCount
0
LastActivityDate
2012-09-28T16:02:14.697
LastEditDate
2012-09-28T16:02:14.697
LastEditorUserId
1432614
OwnerUserId
1432614
ParentId
12633755
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
MySQL will almost always perform better executing straight SQL statements, than looping inside a stored procudure. That said, if you are using InnoDB tables, your procedure will run faster inside a <code>START TRANSACTION</code> / <code>COMMIT</code> block. Even better would be to add an <code>AUTO_INCREMENT</code> to the records in <code>frugg.temp_input</code>, and querying against that table: <pre><code>DROP TABLE IF EXISTS temp_input2; CREATE TABLE temp_input2 ( id INT UNSIGNED NOT NULL AUTO_INCREMENT, shortProductDescription TEXT, longProductDescription TEXT, productID INT, productImageURL TEXT, PRIMARY KEY (id) ); START TRANSACTION; INSERT INTO temp_input2 SELECT NULL AS id, shortProductDescription, longProductDescription, productID, productImageURL FROM frugg.temp_input; INSERT INTO item ( id, short_description, long_description ) SELECT id, shortProductDescription AS short_description, longProductDescription AS long_description FROM temp_input2 ORDER BY id; INSERT INTO item_catalog_map ( catalog_id, catalog_unique_item_id, item_id ) SELECT 1 AS catalog_id, CAST(productID AS CHAR) AS catalog_unique_item_id, id AS item_id FROM temp_input2 ORDER BY id; INSERT INTO item_images ( item_id, original_url ) SELECT id AS item_id, productImageURL AS original_url FROM temp_input2 ORDER BY id; COMMIT; </code></pre> Even better than the above, is before loading the .CSV file into <code>frugg.temp_input</code>, you add an <code>AUTO_INCREMENT</code> field to it, saving you the extra step of creating/loading <code>temp_input2</code> shown above.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPerformance of MySQL very bad when stored procedure iterates over large table of 15M rows
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USRoss Smith II
UserOwnerUserId
1. USRoss Smith II
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPerformance of MySQL very bad when stored procedure iterates over large table of 15M rows
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.