The Ultimate Guide to High Availability with MariaDB

Comments - Update Statement for a Varchar Field Causes Separate TimeStamp Field to Update to Current TimeStamp

 
5 years, 6 months ago Ian Gilfillan
Re: Update Statement for a Varchar Field Causes Separate TimeStamp Field to Update to Current TimeStamp [Answer]

You don't provide the table definition (DESC tps), but the timestamp field probably has the ON UPDATE CURRENT_TIMESTAMP clause. See TIMESTAMP. You can use DATETIME instead, remove the clause or use a second timestamp field.

 
5 years, 6 months ago Chris Suttle
Re: Update Statement for a Varchar Field Causes Separate TimeStamp Field to Update to Current TimeStamp

Thank you Ian, this in fact was my issue.

Thanks, Chris

 
5 years, 6 months ago Chris Suttle
Re: Update Statement for a Varchar Field Causes Separate TimeStamp Field to Update to Current TimeStamp

"and I verify that the TransDateTime contains each day's associated transactions" should read "and I verify that the TransDateTime for each row is accurate and represents the transaction's actual logged time".

 
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.