StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POIs this a MySQLi bug? Returned fields are truncated to 8193 bytes under certain circumstances
primarykey
Id
7186282
data
AcceptedAnswerId
9300774
AnswerCount
2
ClosedDate
CommentCount
5
CommunityOwnedDate
CreationDate
2011-08-25T07:01:10.003
FavoriteCount
0
LastActivityDate
2012-02-15T20:25:24.803
LastEditDate
2011-08-25T19:59:42.310
LastEditorUserId
9867
OwnerUserId
9867
ParentId
0
PostTypeId
1
Score
2
ViewCount
506
LastEditorDisplayName
text
Body
When I SELECT a Geometry column with <code>AsText()</code>, the returned value is truncated to 8193 bytes. This looks like a bug to me, but I'd like to post here first to see if I'm missing anything with the way prepared statements work under MySQLi. Are there any settings I'm overlooking here? Chances are I either I'm Doing It Wrong, or there is a setting I don't know about. All test cases below except the first truncate the <code>geom</code> field to 8193 bytes. I'm pulling my hair out trying to determine the cause of this. PHP Version: <code>PHP 5.3.3-7 with Suhosin-Patch (cli) (built: Jan 5 2011 12:52:48)</code> MySQL Version: <code>mysql Ver 14.12 Distrib 5.0.32, for pc-linux-gnu (i486) using readline 5.2</code> <pre class="lang-php prettyprint-override"><code><?php $con = new mysqli(HOST, USER, PASS, DB); $con->query("DROP TABLE IF EXISTS `mytable`"); $con->query("CREATE TABLE `mytable` (`text` TEXT , `geom` GEOMETRY)"); for ($i = 0; $i < 1300; ++$i) { $points[] = "$i $i"; } $wkt = "LINESTRING(" . implode(',', $points) . ")"; $con->query("INSERT INTO `mytable` (`text`,`geom`) VALUES ('$wkt', GeomFromText('$wkt'))"); /* CASE #1 */ echo "With store_result(), no string function on `text`:\n"; $stmt = $con->prepare('SELECT `text`, ASTEXT(`geom`) FROM `mytable`'); $stmt->execute(); $stmt->store_result(); $stmt->bind_result($text, $geom); $stmt->fetch(); $stmt->close(); echo " Text is ".strlen($text)." bytes, Geom is ".strlen($geom)." bytes\n"; unset($text); unset($geom); /* CASE #2 */ echo "With store_result(), left(`text`,10791):\n"; $stmt = $con->prepare('SELECT LEFT(`text`,10791), ASTEXT(`geom`) FROM `mytable`'); $stmt->execute(); $stmt->store_result(); $stmt->bind_result($text, $geom); $stmt->fetch(); $stmt->close(); echo " Text is ".strlen($text)." bytes, Geom is ".strlen($geom)." bytes\n"; unset($text); unset($geom); /* CASE #3 */ echo "With store_result(), only the `geom` column:\n"; $stmt = $con->prepare('SELECT ASTEXT(`geom`) FROM `mytable`'); $stmt->execute(); $stmt->store_result(); $stmt->bind_result($geom); $stmt->fetch(); $stmt->close(); echo " Text is ".@strlen($text)." bytes, Geom is ".strlen($geom)." bytes\n"; unset($text); unset($geom); /* CASE #4 */ echo "Without store_result(), no string function on `text`:\n"; $stmt = $con->prepare( 'SELECT `text`, ASTEXT(`geom`) FROM `mytable`'); $stmt->execute(); $stmt->bind_result($text, $geom); $stmt->fetch(); $stmt->close(); echo " Text is ".strlen($text)." bytes, Geom is ".strlen($geom)." bytes\n"; ?> </code></pre> Expected Result: <pre><code>With store_result(), no string function on `text`: Text is 10791 bytes, Geom is 10791 bytes With store_result(), left(`text`,10791): Text is 10791 bytes, Geom is 10791 bytes With store_result(), only the `geom` column: Text is 0 bytes, Geom is 10791 bytes Without store_result(), no string function on `text`: Text is 10791 bytes, Geom is 10791 bytes </code></pre> Here is my actual result when running the above: <pre><code>With store_result(), no string function on `text`: Text is 10791 bytes, Geom is 10791 bytes With store_result(), left(`text`,10791): Text is 10791 bytes, Geom is 8193 bytes With store_result(), only the `geom` column: Text is 0 bytes, Geom is 8193 bytes Without store_result(), no string function on `text`: Text is 10791 bytes, Geom is 8193 bytes </code></pre>
Tags
<php><mysqli>
Title
Is this a MySQLi bug? Returned fields are truncated to 8193 bytes under certain circumstances
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USwillpall
UserOwnerUserId
1. USwillpall
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POIs this a MySQLi bug? Returned fields are truncated to 8193 bytes under certain circumstances
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POIs this a MySQLi bug? Returned fields are truncated to 8193 bytes under certain circumstances
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.