[MDEV-5488] \W client command does not work well with DELIMITER Created: 2013-12-24  Updated: 2014-01-19  Resolved: 2014-01-19

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 5.1.67, 5.2.14, 5.3.12, 5.5.34, 10.0.7
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Federico Razzoli Assignee: Sergei Golubchik
Resolution: Not a Bug Votes: 0
Labels: upstream


 Description   

I found this bug adding \W at the beginning of a batch file, but I can write a command-line test case:

MariaDB [stk_apalog]> \W
 
Show warnings enabled.
 
MariaDB [stk_apalog]> DELIMITER ||
 
MariaDB [stk_apalog]> CREATE DATABASE IF NOT EXISTS test;
 
    -> DO NULL;
 
    -> ||
 
Query OK, 1 row affected, 1 warning (0.00 sec)
 
 
 
Query OK, 0 rows affected (0.00 sec)

The || delimiter runs 2 statements in this case. If the first statement generates a warning, the warning does not appear. By deleting USE NULL and retrying, the warning appears.

 Comments   
Comment by Elena Stepanova [ 2013-12-30 ]

I actually see some logic in the current behavior.
\W is a client option that means "Enable display of warnings after each statement"
DELIMITER means a separator between statements from the client's point of view.
Thus, after we set it to a non-';' value, for the client the whole composition of CREATE and DO is a single statement; and when it's fully executed, it produces no warnings.

However, I"m not sure if it's designed this way or I'm just inventing excuses, so I'll leave it to somebody else to decide.

Comment by Sergei Golubchik [ 2014-01-19 ]

Expected behavior. \W tells mysql to issue an automatic SHOW WARNINGS every time after sending a statement to the server (and reading its results, if any). In your test case you ask mysql to send two staments at once, in one mysql_real_query() call. There is no way it can squeeze a SHOW WARNINGS in the middle of it.

Generated at Thu Feb 08 07:04:46 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.