Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Not a Bug
-
10.2.7
-
None
Description
10.2.7 version has an issue that doesn't exist in previous version 10.2.6 :
information_schema.columns Column_default now return 'NULL' instead of null
Attachments
Issue Links
- causes
-
CONJ-506 column metadata return 'null' in place of null for server 10.2.7
-
- Closed
-
- is caused by
-
MDEV-13132 Information Schema does not show whether column default is expression or literal
-
- Closed
-
- relates to
-
MDEV-13244 `DEFAULT` & `COMMENT` doens't work sometimes.
-
- Stalled
-
-
MDEV-14053 Unquoted NULL default values in information schema with views
-
- Closed
-
Hi Sergei,
I digged a bit into implications by fixing doctrine... One thing that I would like you to be aware:
> We've tried to reduce the damage by doing this change only in 10.2 (not in 10.1 or 10.0 or 5.5)
Two things:
1. In 10.2.6 (stable) it was working... yet I understand. But this fix have a lot of implications
2. Packaging issue, the official ppa set a version like '5.5.5-10.2.8-MariaDB-10.2.8+maria~xenial-log'. Which means that from PHP, we cannot trust the `mysqli->server_version` (returns 50505), but need to parse 'mysqli->server_info' with so many packaging differences (10.0.15-MariaDB-1~wheezy, ...). This is really painfull. I know this is not directly related, but if the packaging version pretend to be compatible with 5.5.5, it must be the case. Otherwise you should repackage with '10.2.8-MariaDB-10.2.8+maria~xenial-log' or '10.2.8-MariaDB+maria~xenial-log
Just to let you know... but mariadb will probably suffer from this.