Details
-
Bug
-
Status: Stalled (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.2.6
-
Windows 7 x64
Description
I was working on Windows 7 and developing a Laravel project with MariaDB 10.2.6.
The bug was found when I tried to define a datatable:
CREATE TABLE `users` (
|
`id` int(10) UNSIGNED NOT NULL,
|
`name` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
|
`email` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
|
`password` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL COMMENT 'null when sign-up via oauth',
|
`message` int(11) NOT NULL DEFAULT '0' COMMENT 'Id of the last message that has been read',
|
`remember_token` varchar(100) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
|
`created_at` timestamp NULL DEFAULT NULL,
|
`updated_at` timestamp NULL DEFAULT NULL
|
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
|
The columns `password` and `message` are both defined with default value and comment. However, column `message` is not what defined as the above SQL lines.
I tested this carefully on my windows, but I was not able to get access to the Internet on that machine.
Attachments
Issue Links
- relates to
-
MDEV-13341 information_schema.columns Column_default now return 'null' instead of null
- Closed
- links to