diff options
| author | unknown <ramil/ram@mysql.com/ramil.myoffice.izhnet.ru> | 2007-02-08 11:56:18 +0400 |
|---|---|---|
| committer | unknown <ramil/ram@mysql.com/ramil.myoffice.izhnet.ru> | 2007-02-08 11:56:18 +0400 |
| commit | 34d20085f320334e7d6e561d8f85a90f31fa784a (patch) | |
| tree | 6300cc8b4cce39b06e735126668d78b5934cb6e2 /heap/hp_create.c | |
| parent | 31aee856d83684d4f53e6037d02e1240f694e7cb (diff) | |
| download | mariadb-git-34d20085f320334e7d6e561d8f85a90f31fa784a.tar.gz | |
Fix for bug #25301: Non-zero dates with year 0000 are invalid
The 0000 year is valid.
The ISO standard for "Representation of dates and times" says:
"Calendar years are numbered in ascending order according to the
Gregorian calendar by values in the range [0000] to [9999]."
Reverted fix for 21789: DATETIME with 0000-00-00 11:22:33 should be invalid, but is accepted
as it's not a bug.
Fix for 19370: DateTime datatype in MySQL has two bugs in it
will be reverted during 4.1 -> 5.0 merging as it was pushed to the
5.0 tree.
mysql-test/r/date_formats.result:
Fix for bug #25301: Non-zero dates with year 0000 are invalid
- reverted fix for bug #21789: DATETIME with 0000-00-00 11:22:33 should be invalid, but is accepted
sql-common/my_time.c:
Fix for bug #25301: Non-zero dates with year 0000 are invalid
- reverted fix for bug #21789: DATETIME with 0000-00-00 11:22:33 should be invalid, but is accepted
Diffstat (limited to 'heap/hp_create.c')
0 files changed, 0 insertions, 0 deletions