Export - CSV (All fields)
Export - CSV (Current fields)
MDEV-34245
Inconsistent Timestamp Precision with DATE_ADD Function Between MySQL and MariaDB
Extension of timestamp range can cause OM=>NS replication discrepancy and failure
FROM_UNIXTIME(0) used in WHERE gives warning and results in no data being returned
uhelpful error message for timedate in the DST non-existing hour
Close-to-zero timestamps are converted into zero upon aggregation
Assertion `is_valid_time_slow()' failed in Time::valid_MYSQL_TIME_to_valid_value
JSON_TABLE: TIMESTAMP column is always created as NOT NULL with explicit_defaults_on_timestamp=OFF
MIN(timestamp) returns wrong result for near-zero times
Result differs with DESC index upon comparison of timestamp with incompatible value
Aggregate functions lose microseconds for timestamps below 1
week() and ISO 8601
NO_ZERO_DATE affects timestamp values without any warnings
Warning caused by NO_ZERO_DATE is different for TIMESTAMP and other date-related columnsMDEV-17824
Convert between UTC datetime and UNIX timestamps without referencing timezone
Inconsistency between DATE(11111) and DATE('11111')
Confusing warning when using datetimes with year>9999 in the binary protocol
current_timestamp variable being replaced in create table statement
timestamp virtual column yields syntax error in show create table
Make "constant_string_expr+interval" look inside the constant to detect a correct data type
Bad value inserted into a TIME field on truncation
MySQL WL#6292 - Make TIMESTAMP columns nullable by default
The yearweek() and week() functions return a wrong value
Inconsistent warnings when inserting a DATETIME-alike data into a TIME column
CAST(TIME'10:10:10' AS DATE) - regression
GREATEST(date, time) returns a wrong data type
Difference between DATE(int_expression) and DATE(int_field)
No warning when comparing a DATETIME column to a negative TIME value
Wrong result from ADDDATE(IFNULL(baddate))
Keywords UTC_DATE, UTC_TIME, UTC_TIMESTAMP should be non-reserved
Convert old temporal types on ALTER TABLE ... FORCE
Make explicit_defaults_for_timestamp dynamic
EXTRACT(HOUR ....) gives incorect value when hour > 23
Timezone problem
main.timezone fails on sparc
Inconsistent handling of 2-digit year in const and column
Bad results when casting DATE_ADD(..) to some numeric types
CONVERT_TZ adds subsecond digits when converting from CHAR/VARCHAR column value
TIMESTAMP has 2-level logic for default values
MySQL time is not aware of timezone settings
NULLIF does not work as documented
Wrong warning for CAST(TIME('10:20:30') AS DATE) + INTERVAL 1 DAY
Out of range error in AVG(YEAR(datetime)) due to a wrong data type
ROW END needs to be adjusted to 32-bit timestamp upon OM => NS replication
Columnstore does not support 32-bit timestamps: CAL0001: MCS-2025: Data truncated for column
Time type addition error
SIGABRT due to dereferencing a null Item pointer occurs in Item::val_native()
Inconsistent Comparison Results for DATETIME and String Values Between MySQL 5.7 and MariaDB
The TIMESTAMP value of '1970-01-01 00:00:00' can be indirectly inserted in strict mode
Zero datetime reinterprets as '1970-01-01 00:00:00' on field_datetime=field_timestamp
unix_timestamp(coalesce(timestamp_column)) returns NULL on '1970-01-01 00:00:00.000001'