[MDEV-18143] mysql_stmt_fetch return code is wrong if buffer size is 1 Created: 2019-01-05  Updated: 2019-05-09  Resolved: 2019-05-09

Status: Closed
Project: MariaDB Server
Component/s: libmariadb
Affects Version/s: 10.3.11
Fix Version/s: 10.3.13

Type: Bug Priority: Major
Reporter: Daniël van Eeden Assignee: Georg Richter
Resolution: Fixed Votes: 0
Labels: Compatibility
Environment:

Fedora 29


Attachments: File mariadb103_prepare_zerofil.c     File test.sh    
Issue Links:
Relates
relates to CONC-407 mysql_stmt_fetch: required buffer for... Open

 Description   

mysql_stmt_fetch() returns 0 instead of 101 when results are bound to a buffer of size 1 and the data is longer than 1.

Output of the attached test case:

$ ./test.sh 
Client compile version: 80013
Client runtime version: 8.0.13
Server version: 80013
Result: 00001
 
Buffer length: 1
mysql_stmt_fetch result: 101
Result: 0 (prepared statement)
 
Buffer length: 2
mysql_stmt_fetch result: 101
Result: 00 (prepared statement)
 
Buffer length: 3
mysql_stmt_fetch result: 101
Result: 000 (prepared statement)
 
Buffer length: 4
mysql_stmt_fetch result: 101
Result: 0000 (prepared statement)
 
Buffer length: 5
mysql_stmt_fetch result: 0
Result: 00001 (prepared statement)
Client compile version: 100311
Client runtime version: 10.3.11
Server version: 100311
Result: 00001
 
Buffer length: 1
mysql_stmt_fetch result: 0
Result: 1. (prepared statement)
 
Buffer length: 2
mysql_stmt_fetch result: 101
Result: 00 (prepared statement)
 
Buffer length: 3
mysql_stmt_fetch result: 101
Result: 000 (prepared statement)
 
Buffer length: 4
mysql_stmt_fetch result: 101
Result: 0000 (prepared statement)
 
Buffer length: 5
mysql_stmt_fetch result: 0
Result: 00001 (prepared statement)

For buffer length 0..4 the expected result is 101 (MYSQL_DATA_TRUNCATED)
For buffer length 5 the result should be 0



 Comments   
Comment by Daniël van Eeden [ 2019-01-06 ]

This is related to

Comment by Daniël van Eeden [ 2019-03-05 ]

Looks like this might have been fixed in 10.3.13

Comment by Daniël van Eeden [ 2019-03-05 ]

I can confirm that this is fixed in either 10.3.12 or 10.3.13

Comment by Sergei Golubchik [ 2019-05-09 ]

Thanks!

Generated at Thu Feb 08 08:41:49 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.