StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2570270
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-04-03T04:57:18.837
FavoriteCount
0
LastActivityDate
2010-04-03T04:57:18.837
LastEditDate
LastEditorUserId
0
OwnerUserId
207082
ParentId
2558453
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
I've been testing this myself, and I've come up with pretty consistent results. (Even though my tests are a tad crude.) I've tested three computers <ol> <li>Windows 7 (x64), PHP 5.3, MySQL 5.1 </li> <li>Ubuntu 9.10 (x64) PHP 5.2, MySQL 5.1</li> <li>Ubuntu 10.04 (x32) PHP 5.3, MySQL 5.1</li> </ol> So far the tests on all three platforms have indicated the same tings: <ul> <li>Inserting into a BLOB is 2x to 8x faster on MyISAM than on InnoDB. The difference seems to be higher on binary strings than HEX-coded strings. (See the data below)</li> <li>Using a HEX coded string (<code>bin2hex</code> into a <code>X'...'</code>) uses more memory, on average, than using an escaped binary string (<code>mysql_real_escape_string</code> on the raw data). - This seems true for both MyISAM and InnoDB.</li> <li>The binary string is faster on MyISAM, but the HEX-coded data is faster on InnoDB.</li> </ul> <hr> The test was basically just a simple loop that escaped or hex-coded the raw data (a 2.4 MiB image retrieved once at the top of the script), constructed the query string, and executed it via the <code>mysql_query</code> or <code>mysqli::query</code> functions. - I tested with both extensions. Didn't seem to be any difference. I put the results from the Ubuntu 10.04 (#3) up in spreadsheets. The results from the Ubuntu 9.10 (#2) machine were pretty much the same, so I didn't bother set them up: (Finally an excuse to test the Google Docs thing properly! xD) <ul> <li><a href="http://spreadsheets.google.com/ccc?key=0AsQ8-jk24zuwdHN5YkVaMUtZaHdJRGxGWW1uNVBPVVE&hl=en" rel="noreferrer">Binary string on MyISAM</a></li> <li><a href="http://spreadsheets.google.com/ccc?key=0AsQ8-jk24zuwdGplbWtFYUprZzk0Rjh1elVtQjA4b2c&hl=en" rel="noreferrer">HEX-coded string on MyISAM</a></li> <li><a href="http://spreadsheets.google.com/ccc?key=0AsQ8-jk24zuwdE1ja1llOThyNER0MVBIamNUMTEzREE&hl=en" rel="noreferrer">Binary string on InnoDB</a></li> <li><a href="http://spreadsheets.google.com/ccc?key=0AsQ8-jk24zuwdDNTd25ZVDlfd2xsdVpVc1ZNMWZEUEE&hl=en" rel="noreferrer">Hex-coded string on InnoDB</a></li> </ul> These graphs show the private memory usage by the <code>mysqld</code> process on the Win7 (#1) machine. <ul> <li><a href="http://atli.advefir.com/images/hexbin1/myisam_bin_1.gif" rel="noreferrer">Binary string on MyISAM</a></li> <li><a href="http://atli.advefir.com/images/hexbin1/myisam_hex_1.gif" rel="noreferrer">HEX-coded string on MyISAM</a></li> <li><a href="http://atli.advefir.com/images/hexbin1/innodb_bin_1.gif" rel="noreferrer">Binary string on InnoDB</a></li> <li><a href="http://atli.advefir.com/images/hexbin1/innodb_hex_1.gif" rel="noreferrer">HEX-coded string on InnoDB</a></li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy use bin2hex when inserting binary data from PHP into MySQL?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAtli
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
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
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.