[CONC-179] federatedx fails in bb-10.2-connector-c-integ Created: 2016-05-11  Updated: 2019-06-13  Resolved: 2016-05-15

Status: Closed
Project: MariaDB Connector/C
Component/s: None
Affects Version/s: None
Fix Version/s: 3.0.1

Type: Bug Priority: Major
Reporter: Vladislav Vaintroub Assignee: Georg Richter
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
blocks MDEV-9267 pull in Connector/C sources into the ... Closed

 Description   

See http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest/builds/5947/steps/test_7/logs/stdio

the test uses --ps-protocol.
Some warnings are missing

CURRENT_TEST: federated.federatedx
--- /mnt/buildbot/build/mariadb-10.2.0/mysql-test/suite/federated/federatedx.result	2016-05-10 23:55:59.000000000 +0300
+++ /mnt/buildbot/build/mariadb-10.2.0/mysql-test/suite/federated/federatedx.reject	2016-05-11 07:57:14.000000000 +0300
@@ -1019,8 +1019,6 @@
 `blurb` text default '',
 PRIMARY KEY (blurb_id))
 DEFAULT CHARSET=latin1;
-Warnings:
-Warning	1101	BLOB/TEXT column 'blurb' can't have a default value
 connection master;
 DROP TABLE IF EXISTS federated.t1;
 CREATE TABLE federated.t1 (
@@ -1030,8 +1028,6 @@
 ENGINE="FEDERATED"
   DEFAULT CHARSET=latin1
 CONNECTION='mysql://root@127.0.0.1:SLAVE_PORT/federated/t1';
-Warnings:
-Warning	1101	BLOB/TEXT column 'blurb' can't have a default value
 INSERT INTO federated.t1 VALUES (1, " MySQL supports a number of column types in several categories: numeric types, date and time types, and string (character) types.  This chapter first gives an overview of these column types, and then provides a more detailed description of the properties of the types in each category, and a summary of the column type storage requirements.  The overview is intentionally brief.  The more detailed descriptions should be consulted for additional information about particular column types, such as the allowable formats in which you can specify values.");
 INSERT INTO federated.t1 VALUES (2, "All arithmetic is done using signed BIGINT or DOUBLE values, so you should not use unsigned big integers larger than 9223372036854775807 (63 bits) except with bit functions! If you do that, some of the last digits in the result may be wrong because of rounding errors when converting a BIGINT value to a DOUBLE.");
 INSERT INTO federated.t1 VALUES (3, " A floating-point number.  p represents the precision. It can be from 0 to 24 for a single-precision floating-point number and from 25 to 53 for a double-precision floating-point number. These types are like the FLOAT and DOUBLE types described immediately following.  FLOAT(p) has the same range as the corresponding FLOAT and DOUBLE types, but the display size and number of decimals are undefined.  ");
 
mysqltest: Result length mismatch
 
 - saving '/mnt/buildbot/build/mariadb-10.2.0/mysql-test/var/2/log/federated.federatedx-X/' to '/mnt/buildbot/build/mariadb-10.2.0/mysql-test/var/log/federated.federatedx-X/'
 
Retrying test federated.federatedx, attempt(2/3)...



 Comments   
Comment by Vladislav Vaintroub [ 2016-05-15 ]

The error occurs with --ps-protocol means that

perl mysql-test-run.pl --ps-protocol federatedx

fails, while

perl mysql-test-run.pl federatedx

passes

I suspect that warnings are lost for prepared statements

Comment by Georg Richter [ 2016-05-15 ]

Fixed in rev. 9d51d5e3d63b4dd95e708bad9f8f417f8352df2d

  • Fixed offset for warning_count in ps protocol
  • Added new api function mysql_stmt_warning_count
  • For backwards compatibility we also update the value formysql_warning_count function
Comment by Vladislav Vaintroub [ 2016-05-15 ]

Why do we need new API mysql_stmt_warning_count? we can't execute multiple stmts the same time, so mysql_warning_count representing the warning of the last statement (prepared or not) identifies warning count without ambiguity.

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