diff options
| author | unknown <timour@askmonty.org> | 2012-10-17 15:43:56 +0300 |
|---|---|---|
| committer | unknown <timour@askmonty.org> | 2012-10-17 15:43:56 +0300 |
| commit | bc4a456758c8077e5377b8cfaed60af4311653a0 (patch) | |
| tree | b4689bc3028c30ad38355adbb4d574db5cb57437 /sql/sp.cc | |
| parent | 620d14f8c3521f9ec7283b8690e0e16434739d33 (diff) | |
| download | mariadb-git-bc4a456758c8077e5377b8cfaed60af4311653a0.tar.gz | |
MDEV-452 Add full support for auto-initialized/updated timestamp and datetime
Generalized support for auto-updated and/or auto-initialized timestamp
and datetime columns. This patch is a reimplementation of MySQL's
"WL#5874: CURRENT_TIMESTAMP as DEFAULT for DATETIME columns". In order to
ease future merges, this implementation reused few function and variable
names from MySQL's patch, however the implementation is quite different.
TODO:
The only unresolved problem in this patch is the semantics of LOAD DATA for
TIMESTAMP and DATETIME columns in the cases when there are missing or NULL
columns. I couldn't fully comprehend the logic behind MySQL's behavior and
its relationship with their own documentation, so I left the results to be
more consistent with all other LOAD cases.
The problematic test cases can be seen by running the test file function_defaults,
and observing the test case differences. Those were left on purpose for discussion.
Diffstat (limited to 'sql/sp.cc')
| -rw-r--r-- | sql/sp.cc | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/sql/sp.cc b/sql/sp.cc index a1ff4db375b..0d9bbb37ede 100644 --- a/sql/sp.cc +++ b/sql/sp.cc @@ -1350,7 +1350,6 @@ sp_update_routine(THD *thd, stored_procedure_type type, sp_name *name, } store_record(table,record[1]); - table->timestamp_field_type= TIMESTAMP_NO_AUTO_SET; ((Field_timestamp *)table->field[MYSQL_PROC_FIELD_MODIFIED])->set_time(); if (chistics->suid != SP_IS_DEFAULT_SUID) table->field[MYSQL_PROC_FIELD_SECURITY_TYPE]-> |