Integer width deprecated

Discussion of open issues, suggestions and bugs regarding database management and administration tools for MySQL
Post Reply
Zero-G.
Posts: 398
Joined: Sat 09 Dec 2006 12:20

Integer width deprecated

Post by Zero-G. » Mon 02 Nov 2020 20:43

Hey

In mySQL 8, there is a Warning, when creating a field with integer incl. precision.
"Warning: #1681 Integer display width is deprecated and will be removed in a future release."

Will there be a possibility to create backups from older versions, which take care about this warning!?
THX a lot in advance

dzhanhira
Devart Team
Posts: 239
Joined: Mon 26 Oct 2020 13:49

Re: Integer width deprecated

Post by dzhanhira » Tue 03 Nov 2020 07:34

this Warning does not affect the performance of the script, but we will try to add the ability to ignore the dimension of this data type in one of the the next version.

gork
Posts: 1
Joined: Wed 20 Apr 2022 22:17

Re: Integer width deprecated

Post by gork » Wed 20 Apr 2022 22:28

I am having a related problem with MySQL 8.0.21 (Percona XtraDB Cluster) which appears related to deprecated integer width: When doing an DB compare from a project or script directory, all integer columns are detected as modified unless I ignore column data types when doing the compare.

A SHOW CREATE TABLE query returns the column type as INT however dBforge always interprets this as INT(11) and displays INT(11) in the source and target comparison windows even when both the sql file in the project directory and the target table specify the column data type as INT and not INT(11).

This problem significantly hobbles all db comparison and related features. Is there any way to have dbForge /not/ force a width argumennt on integer data types? Even when using the Generate Script > CREATE feature, dbForge injects (11) onto the column type.

Post Reply