When editing row, the UI would choose NOW function as default even if TIMESTAMP col was not empty. This resulted in resetting the col to the current timestamp.
The patch adds test for the data when deciding whether to use default function for 'first timestamp' or not. The patch is against version 3.3.5
View and moderate all "patches Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Patches"
Thanks for the patch but I cannot reproduce this problem under version 3.3.8. If you can, give me a scenario.
Patch merged for 3.3.9.