PEAK XOOPS - TIMESTAMP column in protector_log table 
TIMESTAMP column in protector_log table
- You cannot open a new topic into this forum
- Guests cannot post into this forum
Previous post
-
Next post
|
Parent
-
Children.1
|
Posted on 2006/10/13 0:34
Dave_L
From: Virginia, USA
Posts: 35
From: Virginia, USA
Posts: 35
[Feature change request]
The TIMESTAMP column in the protector_log table is causing some issues with compatibility across different MySQL versions, when using mysqldump to export databases from one version to another.
Since rows are only inserted into that table, and never updated, I don't see any real benefit to using the TIMESTAMP column type.
I suggest changing that column type to DATETIME, and manually setting it when a row is inserted in that table:
INSERT INTO `protector_log` ... `timestamp`=NOW()
The TIMESTAMP column in the protector_log table is causing some issues with compatibility across different MySQL versions, when using mysqldump to export databases from one version to another.
Since rows are only inserted into that table, and never updated, I don't see any real benefit to using the TIMESTAMP column type.
I suggest changing that column type to DATETIME, and manually setting it when a row is inserted in that table:
INSERT INTO `protector_log` ... `timestamp`=NOW()
Votes:1
Average:10.00
GIJOE
Posts: 4110
Posts: 4110
hi Dave_L.
Certainly, TIMESTAMP is hard to use. (version incompatibity is also fatal)
I'll modify it in the next major version.
Certainly, TIMESTAMP is hard to use. (version incompatibity is also fatal)
I'll modify it in the next major version.
Votes:0
Average:0.00
Previous post
-
Next post
|
Parent
-
No child
|
Posted on 2006/10/19 4:45
Dave_L
From: Virginia, USA
Posts: 35
From: Virginia, USA
Posts: 35
Thanks 
Votes:0
Average:0.00
Login