CURRENT_TIMESTAMP: different mysql-behavior phpmyadmin vs. CI

CURRENT_TIMESTAMP: different mysql-behavior phpmyadmin vs. CI

kbs170
Newbie
Posts: 5
Threads: 2
Joined: Oct 2018
Reputation: 0

11-29-2018, 08:36 AM

I found the mistake. There is a bundle of UPDATEs before that. All without modified=NOW() but - of course - mysql set "modified" automatically (because of ON UPDATE CURRENT_TIMESTAMP).

Sorry, and thank you for your support.

Best,

Messages In This Thread

CURRENT_TIMESTAMP: different mysql-behavior phpmyadmin vs. CI - by kbs170 - 11-29-2018, 05:29 AM

RE: CURRENT_TIMESTAMP: different mysql-behavior phpmyadmin vs. CI - by Pertti - 11-29-2018, 06:09 AM

RE: CURRENT_TIMESTAMP: different mysql-behavior phpmyadmin vs. CI - by kbs170 - 11-29-2018, 06:22 AM

RE: CURRENT_TIMESTAMP: different mysql-behavior phpmyadmin vs. CI - by Pertti - 11-29-2018, 06:38 AM

RE: CURRENT_TIMESTAMP: different mysql-behavior phpmyadmin vs. CI - by kbs170 - 11-29-2018, 08:36 AM

RE: CURRENT_TIMESTAMP: different mysql-behavior phpmyadmin vs. CI - by InsiteFX - 11-29-2018, 10:06 AM