[MDEV-15377] 10.2+ Integer DEFAULT values missing quotes Created: 2018-02-21  Updated: 2018-03-13  Resolved: 2018-03-13

Status: Closed
Project: MariaDB Server
Component/s: Documentation
Affects Version/s: 10.2
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Nemanja Stambolic Assignee: Ian Gilfillan
Resolution: Fixed Votes: 0
Labels: None
Environment:

GNU/Linux

Issue Links:
PartOf
includes MDEV-15394 DEFAULT current_timestamp() discrepancy Closed
Relates
relates to MDEV-15407 DEFAULT NULL forced when no DEFAULT s... Closed
relates to MDEV-15519 CHECKSUM TABLE gives different result... Confirmed
Sub-Tasks:
Key
 Summary
 Type
 Status
 Assignee
MDEV-15390 information_schema returns quoted str... Technical task Closed Ian Gilfillan  
MDEV-15394 DEFAULT current_timestamp() discrepancy Technical task Closed Ian Gilfillan  
MDEV-15407 DEFAULT NULL forced when no DEFAULT s... Technical task Closed Ian Gilfillan  

 Description    

SHOW CREATE TABLE test\G;

MariaDB server 10.0:

  `link` tinyint(1) NOT NULL DEFAULT '1',

MariaDB server 10.2:

  `link` tinyint(1) NOT NULL DEFAULT 1,

I believe this change was intentional - not to quote integers. But both MySQL and MariaDB (prior to 10.2) had been behaving opposite on this - e.g. always quoted DEFAULT values. And now if some app relies on those outputs - it produces bad results across older vs. latest MariaDB server versions. I agree that it is bad to rely on such statements at first place in your app - but in our legacy app that was exactly the case.

I doubt there is a flag to get back the old behavior?

Note that this https://mariadb.com/kb/en/library/show-create-table/ is totally unrelated - that's for column names quotes, not DEFAULT values.



 Comments   
Comment by Elena Stepanova [ 2018-02-21 ]

The change was intentional, introduced by this commit:

commit 6820bf9ca9c5992a7e9d382aa8aaabff6751fd46
 
Author: Sergei Golubchik <serg@mariadb.org>
 
Date:   Tue Jul 19 11:18:58 2016 +0200
 
 
 
    do not quote numbers in the DEFAULT clause in SHOW CREATE

There is no flag to revert to the old behavior.

Maybe the change deserves mentioning in documentation, assigning to greenman to decide.

Comment by Nemanja Stambolic [ 2018-02-22 ]

Thanks for clarification. Kind of expected Documentation at least must cover this indeed.

Comment by Ian Gilfillan [ 2018-03-13 ]

Added in https://mariadb.com/kb/en/library/show-create-table/ and in https://mariadb.com/kb/en/library/incompatibilities-and-feature-differences-between-mariadb-102-and-mysql-57/

Comment by Nemanja Stambolic [ 2018-03-13 ]

Thanks.

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