maria-developers team mailing list archive

[Reindl Harald <h.reindl@xxxxxxxxxxxxx>]

Am 23.04.2018 um 16:17 schrieb Peter Laursen:
> https://dev.mysql.com/doc/refman/8.0/en/numeric-type-overview.html "
> /|M|/ indicates the maximum display width for integer types. The maximum
> display width is 255. Display width is unrelated to the range of values
> a type can contain"

i know that - these days - but it's not logical and expected when you
start to work with this stuff and one of many gotchas

> I just inserted "1111111111" into an INT(5) column and was able to
> create a INT(200) column as well.
> 
> On Mon, Apr 23, 2018 at 3:59 PM, Reindl Harald <h.reindl@xxxxxxxxxxxxx
> <mailto:h.reindl@xxxxxxxxxxxxx>> wrote:
> 
> 
> 
>     Am 23.04.2018 um 15:51 schrieb Alexander Barkov:
>     > Does anybody see any problems if in 10.4 we fix all metadata statements,
>     > such as:
>     > 
>     > - SHOW CREATE TABLE t1
>     > - DESCRIBE t1
>     > - SELECT * FROM INFORMATION_SCHEMA.COLUMNS
>     > not to print the default length for non-ZEROFILL columns?
>     yes - consumer code may rely on parse outputs
> 
>     and frankly i assumed that when i define a unsigned tinyit(2) in can
>     hold 0-99 and would reject -1 oder 100 in strict-mode with an error