From 96ae0b92b22916c10b92c78862f5daf10e2b329d Mon Sep 17 00:00:00 2001 From: unknown Date: Thu, 10 Nov 2005 17:05:19 +0300 Subject: Fix a comment. sql/sql_cursor.cc: A post-review fix for Bug#13488 --- sql/sql_cursor.cc | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) (limited to 'sql/sql_cursor.cc') diff --git a/sql/sql_cursor.cc b/sql/sql_cursor.cc index 07be9efa6ac..fc169fe18e8 100644 --- a/sql/sql_cursor.cc +++ b/sql/sql_cursor.cc @@ -561,12 +561,13 @@ int Materialized_cursor::open(JOIN *join __attribute__((unused))) 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. -- cgit v1.2.1