> On Apr 29, 2018, at 6:24 PM, Robin Chattopadhyay <[email protected]> wrote: > > I use SQLite to create some basic reporting from gnucash and I noticed that > after upgrading from 2.6.x to 3.0/3.1 several of the date fields are now > stored in two different formats: > > Transactions entered in the file under 2.6.x are: yyyymmddhhmmss while > dates entered in the file under 3.0/3/1 are yyyy-mm-dd hh:mm:ss. > > Is this by design? I worked around it by adding a CASE statement to the sql > I was using. >
Yes, so that the date strings are consistent across all three database engines. Regards, John Ralls _______________________________________________ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
