Comments - Timestamps are different

9 years, 7 months ago roberto spadim

use to_unixtimestamp() at plan_approved_on column

do you have the insert query? what binlog are you using row/binary/mixed?

9 years, 7 months ago Tim Rice

Those are all super questions. I don't know the answer to any of them. We have a developer who wrote this web application via php that does all the inserts. I will ask him if they can get me more info.

What I can tell you is what the schema looks like from a MariaDB perspective:

MariaDB [safeplan_new1]> desc plan_approval; +------------------------+-------------------+------+-----+-------------------+-----------------------------+



plan_approved_ontimestampNOCURRENT_TIMESTAMPon update CURRENT_TIMESTAMP


9 years, 7 months ago Tim Rice

To answer your question (sorry that I failed to answer this in the first post), I am using binlog_format=ROW

9 years, 7 months ago roberto spadim


run this query in each server

select to_unixtimestamp(plan_approved_on) from safeplan_new1.plan_approval where plan_approval_id=3247

(i don't know if the problem is the on update at slaves, i never tried it)

check if you have diferrent unixtimestamps for servers

after this we could put this history at jira (mariadb bug tracker -, if we can't solve the error, i'm a mariadb user =]

propably they will ask about insert queires or binlog file

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.