We are getting the below error when an update is done on CROpportunity table.
“Incorrect datetime value: '4095-15-255 255:63:63.1048575' for column 'Tstamp' at row 1”
Column tststamp on the table is defined as
`tstamp` timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP(6) ON UPDATE CURRENT_TIMESTAMP(6),
from my understanding this means if there is no explicit value defined for tststamp, if any update happens the value for tstamp column should be set to current timestamp. Not sure how this invalid value is getting set.
Best answer by vib1980
we did furthermore analysis from our side and found out that there was a configuration change made on our db server (sql_mode is now set to STRICT_TRANS_TABLES).
While updating Opportunity there is a section of code that selects timestamp for the graph.
New restriction on the DB server could be the reason why it’s failing with Incorrect datetime value: '4095-15-255 255:63:63.1048575'. There is another way to set timestamp for the graph from db using PXDatabase.SelectTimeStamp() but unsure what are the underlying impact.
we did furthermore analysis from our side and found out that there was a configuration change made on our db server (sql_mode is now set to STRICT_TRANS_TABLES).
While updating Opportunity there is a section of code that selects timestamp for the graph.
New restriction on the DB server could be the reason why it’s failing with Incorrect datetime value: '4095-15-255 255:63:63.1048575'. There is another way to set timestamp for the graph from db using PXDatabase.SelectTimeStamp() but unsure what are the underlying impact.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.