1 Answer
- Newest
- Most votes
- Most comments
1
Hi,
this kind of error usually comes when the date / timestamp supplied is incorrect and turns the number of corresponding nanoseconds (=nanos) to a negative number given its format.
So, I guess that you have figure out if some values of your 'changed' and 'created' are not too big for the format that you have chosen and turn corresponding values to negative ones. If possible, declare those 'changed' and 'created' as unsigned formats in order to increase the range of their possible values.
Best
Didier
Relevant content
- asked 2 years ago
- asked 4 months ago
- asked a year ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 4 months ago
Thanks you for the answer :)
The columns created and changed will always hold timestamps back in time so I'm not sure how they could be too big to extract the data.
More importantly though, how does this explain that I am able to run the query at any later point without reproducing the error?