Menu
▾
▴
#2674 (ok 2.11.7) Auto_Increment selected for TimeStamp by Default
fixed
1
2013-06-11
2008-04-10
No
When having a TIMESTAMP Field Attributes set to "ON UPDATE CURRENT_TIMESTAMP" when you go into that Field to edit options the Extra is defaulted to "AUTO_INCREMENT". If one does not catch this and they select submit it will create an error. With ON UPDATE CURRENT_TIMESTAMP set to blank it does not default the Attributes to AUTO_INCREMENT.
Discussion
Logged In: YES
user_id=326580
Originator: NO
SHOW FULL FIELDS FROM now includes ON UPDATE CURRENT_TIMESTAMP in Extra
Logged In: YES
user_id=326580
Originator: NO
SHOW FULL FIELDS FROM now includes ON UPDATE CURRENT_TIMESTAMP in Extra
Logged In: YES
user_id=326580
Originator: NO
fixed in SVN, you can test here after next update:
http://pma.cihar.com/QA_2_11/?pma_username=root
Logged In: YES
user_id=1383652
Originator: NO
'on update CURRENT_TIMESTAMP', <-- surplus comma (at least in trunk)
);
Logged In: YES
user_id=326580
Originator: NO
this is intentional, coding standard
(better diff when adding new elements + instead of ~+, more fail-safe)
Logged In: YES
user_id=326580
Originator: NO
as you can see perfectly here: http://wiki.cihar.com/wiki/index.php?title=Config&diff=4844&oldid=prev
with correct comma after 'UNSIGNED ZEROFILL' the diff would have one line less
;-)
Logged In: YES
user_id=1383652
Originator: NO
ok,
is it also intentional that default was only chaned in trunk?
Logged In: YES
user_id=326580
Originator: NO
yes, ON UPDATE CURRENT_TIMESTAMP does not exists in MySQL 3.x and 4.0, as the removed comment says, in phpMyAdmin 2.11 this is added dynamically