Thanks Adam for that information. Yikes! On the found error from 2015!…. I wonder if that got reported as behavior but not investigated. (We do not need you to investigate that… just curious.).
On Tue, Jul 18, 2023 at 3:24 AM Ádám Sághy <adamsa...@gmail.com> wrote: > Hi guys, > > I just wanted to share with you that i am working on enabling microseconds > precision of DATETIME / TIMESTAMP for MySql / MariaDb (By default the > precision is 0 due to backward compatibility reasons: MySql 5.6.3 or > earlier). Postgres is not a problem since it is enabling microseconds > precision by default. > > The above is a necessary step to handle the mentioned issue in the title, > but it is not the only one: > > *Step 1* - Ordering of loan transactions should be based on transaction > date + creation datetime + ID in this order (For years mysql was used > with second precision. That implies keeping the ID in the ordering > sequence.) > > *Step 2* - Set precision of 6 for DATETIME / TIMESTAMP for Mysql / > MariaDB (PostgresDB is not effected, by default it is using precision of 6 > digits after seconds) > *It should not cause any backward compatibility issues by default, but > having more precision we can rely on the ordering by creation date time for > the same day transactions!* > > *Moreover, the* LoanTransactionComparator *was using* creation date time *as > the secondary ordering attribute since 2015!* > > > Regards, > > Adam > -- Sent from Gmail Mobile
