Alexander Barkov
06ebc6cc50
MDEV-4838 Wrong metadata for DATE_ADD('string', INVERVAL)
...
The problem seems to be fixed by some earlier change
and is not reproducible any longer. Only adding a test case.
2013-12-19 12:39:40 +04:00
Sergei Golubchik
d28d3ba40d
10.0-base merge
2013-12-16 13:02:21 +01:00
Sergei Golubchik
6bf10fac44
5.5 merge
2013-12-15 15:57:26 +01:00
Sergei Golubchik
c6d30805db
5.5 merge
2013-11-23 00:50:54 +01:00
Alexander Barkov
c7355b1982
Merge 5.3->5.5
2013-11-21 13:09:08 +04:00
Alexander Barkov
2394fa67d4
MDEV-4859 Wrong value and data type of "SELECT MAX(time_column) + 1 FROM t1"
...
Fixed.
2013-11-21 11:46:36 +04:00
Alexander Barkov
5a8bd446ad
Merge 5.3->5.5
...
pending merges:
Alexander Barkov 2013-12-02 MDEV-4857 Wrong result of HOUR('1 00:00:00')
2013-12-02 15:50:35 +04:00
Alexander Barkov
b97b9536c7
MDEV-4857 Wrong result of HOUR('1 00:00:00')
...
modified:
mysql-test/r/func_time.result
mysql-test/t/func_time.test
sql-common/my_time.c
sql/item_func.h
sql/item_timefunc.cc
sql/mysql_priv.h
sql/time.cc
2013-12-02 15:09:34 +04:00
Sergei Golubchik
9af177042e
10.0-base merge.
...
Partitioning/InnoDB changes are *not* merged (they'll come from 5.6)
TokuDB does not compile (not updated to 10.0 SE API)
2013-09-21 10:14:42 +02:00
Sergei Golubchik
4ec2e9d7ed
5.5 merge and fixes for compiler/test errors
2013-09-18 13:07:31 +02:00
Alexander Barkov
b20deca695
Merge from 5.3
2013-09-16 14:08:43 +04:00
Alexander Barkov
5464e904b6
MDEV-4861 TIME/DATETIME arithmetics does not preserve INTERVAL precision
...
Adding tests only.
The problem was earlier fixed by
MDEV-4724 Some temporal functions do not preserve microseconds
2013-09-16 14:07:01 +04:00
Alexander Barkov
6a5f07ee87
Merge from 5.3
...
pending merges:
Alexander Barkov 2013-09-16 MDEV-4870 Wrong values of CASE, COALESCE, IF...
2013-09-16 13:54:12 +04:00
Alexander Barkov
22c4a24961
MDEV-4870 Wrong values of CASE, COALESCE, IFNULL on a combination of different temporal types
...
Adding test cases from the bug report only.
The problem was earlier fixed by:
MDEV-4863 COALESCE(time_or_datetime) returns wrong results in numeric context
modified:
mysql-test/r/func_time.result
mysql-test/t/func_time.test
2013-09-16 13:52:13 +04:00
Alexander Barkov
f2737b415e
Merge from 5.3
...
pending merges:
Alexander Barkov 2013-09-16 MDEV-4869 Wrong result of MAKETIME(0, 0, -0.1)
2013-09-16 13:08:19 +04:00
Alexander Barkov
6c9d983287
MDEV-4869 Wrong result of MAKETIME(0, 0, -0.1)
...
Adding a test case only.
The problem was fixed by:
MDEV-4724 Some temporal functions do not preserve microseconds
modified:
mysql-test/r/func_time.result
mysql-test/t/func_time.test
2013-09-16 13:03:49 +04:00
Alexander Barkov
2624022b53
Merge from 5.3
...
pending merges:
Alexander Barkov 2013-09-16 MDEV-4843 Wrong data type for TIMESTAMP('200...
2013-09-16 10:51:03 +04:00
Alexander Barkov
5d7b97b89e
MDEV-4843 Wrong data type for TIMESTAMP('2001-01-01','10:10:10')
2013-09-16 10:14:41 +04:00
Alexander Barkov
cf9cc19e91
MDEV-4724 Some temporal functions do not preserve microseconds
2013-09-13 14:43:10 +04:00
Alexander Barkov
51dcf4dcff
Merge from 5.3.
...
pending merges:
Alexander Barkov 2013-09-12 MDEV-4724 Some temporal functions do not pre...
2013-09-13 12:06:17 +04:00
Alexander Barkov
499ddea576
MDEV-4724 Some temporal functions do not preserve microseconds
2013-09-12 21:31:14 +04:00
Alexander Barkov
8b5da9f73b
Merge from 5.3
...
pending merges:
Alexander Barkov 2013-09-09 MDEV-4863 COALESCE(time_or_datetime) returns...
2013-09-10 10:08:11 +04:00
Alexander Barkov
c2b38529a9
MDEV-4863 COALESCE(time_or_datetime) returns wrong results in numeric context
2013-09-09 15:32:25 +04:00
Sergei Golubchik
97e640b9ae
5.5 merge
2013-07-17 21:24:29 +02:00
Alexander Barkov
1f3ec9800c
Merging from 5.3
...
modified:
include/my_time.h
libmysql/libmysql.c
mysql-test/r/adddate_454.result
mysql-test/r/cast.result
mysql-test/r/date_formats.result
mysql-test/r/func_sapdb.result
mysql-test/r/func_time.result
mysql-test/r/mdev316.result
mysql-test/r/parser.result
mysql-test/r/partition_datatype.result
mysql-test/r/partition_pruning.result
mysql-test/r/type_date.result
mysql-test/r/type_datetime.result
mysql-test/suite/vcol/r/vcol_misc.result
mysql-test/t/cast.test
sql-common/my_time.c
sql/field.cc
sql/field_conv.cc
sql/filesort.cc
sql/item.cc
sql/item.h
sql/item_cmpfunc.cc
sql/item_func.cc
sql/item_strfunc.cc
sql/item_timefunc.cc
sql/sql_time.cc
pending merges:
Sergei Golubchik 2013-07-03 MDEV-4667 DATE('string') incompability betwe...
2013-07-08 16:49:42 +04:00
Sergei Golubchik
78cc6db44a
MDEV-4667 DATE('string') incompability between mysql and mariadb
...
Cleanup: remove TIME_FUZZY_DATE.
Introduce TIME_FUZZY_DATES which means "very fuzzy, the resulting
value is only used for comparison. It can be invalid date, fine, as long as it can be
compared".
Updated many tests results (they're better now).
2013-07-03 09:46:20 +02:00
Alexander Barkov
7cc7710679
Merging MDEV-4635 from 5.3.
...
Also, fixing a bug in STR_TO_DATE(). It erroneously returned
error in strict mode for dates like '0000-01-01'
(zero year, but non-zero month and day).
According to the manual:
- NO_ZERO_DATE disallows 0000-00-00 (all date parts are zeros)
- NO_ZERO_IN_DATE disallows zero month (YYYY-00-DD) or day (YYYY-MM-00).
0000-01-01 is a valid date, even in strict mode.
modified:
mysql-test/r/func_time.result
mysql-test/r/strict.result
mysql-test/t/func_time.test
mysql-test/t/strict.test
sql/item_timefunc.cc
sql/sql_time.h
pending merges:
Alexander Barkov 2013-06-17 MDEV-4635 Crash in UNIX_TIMESTAMP(STR_TO_DAT...
2013-06-18 13:14:46 +04:00
Alexander Barkov
4085836acf
MDEV-4635 Crash in UNIX_TIMESTAMP(STR_TO_DATE('2020','%Y'))
...
modified:
mysql-test/r/func_time.result
mysql-test/t/func_time.test
sql/item_timefunc.cc
sql/mysql_priv.h
2013-06-17 19:25:55 +04:00
Sergei Golubchik
993ea79f2d
5.5 merge
2013-03-27 23:41:02 +01:00
Sergei Golubchik
6599fd3e9c
5.3 merge
2013-03-27 10:03:28 +01:00
Sergei Golubchik
1be4295617
MDEV-4293 Valgrind warnings (Conditional jump or move depends on uninitialised value) in remove_eq_conds on time functions with NULL argument
...
val_int() is expected to return 0 for NULL's
2013-03-20 16:13:00 +01:00
Sergei Golubchik
019f7425b7
MDEV-4281 Assertion `maybe_null && item->null_value' fails in make_sortkey on CASE with different return types, GROUP_CONCAT, GROUP BY
...
Fix Item::get_date() to mark the item NULL when returning an error.
2013-03-17 07:41:22 +01:00
Sergei Golubchik
0af4b6c6ee
5.5 merge
2013-01-29 15:10:47 +01:00
Sergei Golubchik
aca8e7ed6b
5.3 merge
2013-01-15 19:07:46 +01:00
Sergei Golubchik
b0ee31c894
MDEV-3942 FROM_DAYS(<timestamp column>) returns different result in MariaDB comparing to MySQL: NULL vs 0000-00-00
...
fixed a regression, introduced while fixing MDEV-456
2013-01-08 21:23:03 +01:00
Michael Widenius
620d14f8c3
Automatic merge
2012-09-22 17:11:40 +03:00
Sergei Golubchik
59408093d1
5.3 merge
2012-08-31 14:15:52 +02:00
Sergei Golubchik
0536c506ff
MDEV-437 Microseconds: In time functions precision is calculated modulo 256
...
store the precision in uint, not uint8
2012-08-30 09:05:27 +02:00
Sergei Golubchik
c562c74478
MDEV-457 Inconsistent data truncation on datetime values with fractional seconds represented as strings with no delimiters
...
New implementation for str_to_datetime. Fix MDEV-457 and related issues.
2012-09-08 12:15:55 +02:00
Sergei Golubchik
f860b2aad4
merge
2012-04-07 15:58:46 +02:00
Sergei Golubchik
a3073ecd96
merge
2012-04-05 23:07:18 +02:00
Sergei Golubchik
dea3544b2d
mysql-5.1.62 merge
2012-04-05 10:49:38 +02:00
Sergei Golubchik
4933d21e5d
merge with mysql-5.5.21
2012-03-09 08:06:59 +01:00
Alexander Barkov
c0badf88c6
Merging BUG#13458237 from 5.1.
2012-01-24 13:24:05 +04:00
Alexander Barkov
f8e924b467
BUG#13458237 - INCONSISTENT HANDLING OF INVALIDE DATES WITH ZERO DAY. SIMILAR TO '2009-10-00'
...
- Reverting the patch for Bug # 12584302
The patch will be reverted in 5.1 and 5.5.
The patch will not be reverted in 5.6, the change will
be properly documented in 5.6.
- Backporting DBUG_ASSERT not to crash on '0000-01-00'
(already fixed in mysql-trunk (5.6))
2012-01-24 13:00:13 +04:00
Alexander Barkov
1522923949
BUG#13354387 - CRASH IN IN MY_DECIMAL::OPERATOR FOR VIEW AND FUNCTION UNIX_TIME
...
Fixing the 5.5 part (the 5.6 part will go in a separate commit soon).
Problem:
Item_direct_ref::get_date() incorrectly calculated its "null_value",
which made UNIX_TIMESTAMP(view_column) incorrectly return NULL
for a NOT NULL view_column.
Fix:
Make Item_direct_ref::get_date() calculate null_value
in the similar way with the other methods
(val_real,val_str,val_int,val_decimal):
copy null_value from the referenced Item.
modified:
mysql-test/r/func_time.result
mysql-test/t/func_time.test
sql/item.cc
2012-01-12 13:02:51 +04:00
Sergei Golubchik
2ccf247e93
after merge changes:
...
* rename all debugging related command-line options
and variables to start from "debug-", and made them all
OFF by default.
* replace "MySQL" with "MariaDB" in error messages
* "Cast ... converted ... integer to it's ... complement"
is now a note, not a warning
* @@query_cache_strip_comments now has a session scope,
not global.
2011-12-12 23:58:40 +01:00
Michael Widenius
6d4224a31c
Merge with 5.2.
...
no_error handling for select (used by INSERT ... SELECT) still needs to be fixed, but I will do that in a separate commit
2011-12-11 11:34:44 +02:00
Sergei Golubchik
d2755a2c9c
5.3->5.5 merge
2011-11-22 18:04:38 +01:00
Michael Widenius
a8d03ab235
Initail merge with MySQL 5.1 (XtraDB still needs to be merged)
...
Fixed up copyright messages.
2011-11-21 19:13:14 +02:00