diff options
| author | konstantin@mysql.com <> | 2004-05-25 19:52:05 +0400 |
|---|---|---|
| committer | konstantin@mysql.com <> | 2004-05-25 19:52:05 +0400 |
| commit | 4eaac5fa56a88dad436d1f4f1a4aa573885d6a5c (patch) | |
| tree | f10d16a5bbfacf06c45b5e92c15370e769f24812 | |
| parent | 391d5629f6cf12ac4dd61e3d8f6cc435ae7b12db (diff) | |
| download | mariadb-git-4eaac5fa56a88dad436d1f4f1a4aa573885d6a5c.tar.gz | |
changed comment for LONG_DATA_COMMAND
| -rw-r--r-- | sql/sql_prepare.cc | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/sql/sql_prepare.cc b/sql/sql_prepare.cc index 18437265e0e..23b87a41c1a 100644 --- a/sql/sql_prepare.cc +++ b/sql/sql_prepare.cc @@ -57,9 +57,9 @@ Long data handling: - Server gets the long data in pieces with command type 'COM_LONG_DATA'. - The packet recieved will have the format as: - [COM_LONG_DATA:1][STMT_ID:4][parameter_number:2][type:2][data] - - Checks if the type is specified by client, and if yes reads the type, - and stores the data in that format. + [COM_LONG_DATA:1][STMT_ID:4][parameter_number:2][data] + - data from the packet is appended to long data value buffer for this + placeholder. - It's up to the client to check for read data ended. The server doesn't care; and also server doesn't notify to the client that it got the data or not; if there is any error; then during execute; the error |