bk commit into 5.0 tree (konstantin:1.1959)

[konstantin]

Below is the list of changes that have just been committed into a local
5.0 repository of kostja. When kostja does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://dev.mysql.com/doc/mysql/en/installing-source-tree.html

ChangeSet
  1.1959 05/11/10 17:05:19 konstantin@stripped +1 -0
  Fix a comment.

  sql/sql_cursor.cc
    1.3 05/11/10 17:05:11 konstantin@stripped +7 -6
    A post-review fix for Bug#13488

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	konstantin
# Host:	dragonfly.local
# Root:	/opt/local/work/mysql-5.0-root

--- 1.2/sql/sql_cursor.cc	2005-11-09 20:30:55 +03:00
+++ 1.3/sql/sql_cursor.cc	2005-11-10 17:05:11 +03:00
@@ -561,12 +561,13 @@
   if (rc == 0)
   {
     /*
-      Now send the result set metadata to the client. We need to do it
-      here, as in Select_materialize::send_fields the exact column types
-      are not yet known. The new types may differ from the original ones
-      sent at prepare if some of them were altered by MySQL HEAP tables
-      mechanism -- used when create_tmp_field_from_item may alter the
-      original column type.
+      Now send the result set metadata to the client. We need to
+      do it here, as in Select_materialize::send_fields the items
+      for column types are not yet created (send_fields requires
+      a list of items). The new types may differ from the original
+      ones sent at prepare if some of them were altered by MySQL
+      HEAP tables mechanism -- used when create_tmp_field_from_item
+      may alter the original column type.
 
       We can't simply supply SEND_EOF flag to send_fields, because
       send_fields doesn't flush the network buffer.