Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.0.0, 5.5.25, 5.3.7
-
None
-
None
Description
CREATE TABLE t (a TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(0));
|
# Query OK, 0 rows affected (0.20 sec)
|
|
|
INSERT INTO t VALUES (NULL);
|
# Query OK, 1 row affected (0.04 sec)
|
|
|
SELECT * FROM t;
|
# +-------------------------+
|
# | a |
|
# +-------------------------+
|
# | 2012-08-07 04:18:48.353 |
|
# +-------------------------+
|
# 1 row in set (0.00 sec)
|
Inserting CURRENT_TIMESTAMP(0) explicitly works as expected:
INSERT INTO t VALUES (CURRENT_TIMESTAMP(0));
|
# Query OK, 1 row affected (0.04 sec)
|
|
|
SELECT * FROM t;
|
# +-------------------------+
|
# | a |
|
# +-------------------------+
|
# | 2012-08-07 04:18:48.353 |
|
# | 2012-08-07 04:23:51.000 |
|
# +-------------------------+
|
# 2 rows in set (0.01 sec)
|
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Fix Version/s | 5.3.9 [ 11000 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Closed [ 6 ] | Reopened [ 4 ] |
| Fix Version/s | 5.5.29 [ 11701 ] | |
| Fix Version/s | 5.3.10 [ 11500 ] | |
| Fix Version/s | 5.3.9 [ 11000 ] | |
| Fix Version/s | 5.5.27 [ 11100 ] |
| Affects Version/s | 10.0.0 [ 10000 ] |
| Fix Version/s | 10.0.0 [ 10000 ] |
| Fix Version/s | 10.0.1 [ 11400 ] | |
| Fix Version/s | 10.0.0 [ 10000 ] |
| Fix Version/s | 5.5.29 [ 12102 ] | |
| Fix Version/s | 5.5.28a [ 11701 ] |
| Status | Reopened [ 4 ] | In Progress [ 3 ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
| Workflow | defaullt [ 13706 ] | MariaDB v2 [ 46019 ] |
| Workflow | MariaDB v2 [ 46019 ] | MariaDB v3 [ 66694 ] |
| Workflow | MariaDB v3 [ 66694 ] | MariaDB v4 [ 144914 ] |
in MySQL it's fixed differently. one might specify a precision, but the precision must match the column's precision. Let's do the same, for compatibility reasons.