On Tue, Feb 23, 2010 at 7:07 AM, Conrad Canterford <[email protected]> wrote: > On Sun, 2010-02-21 at 18:37 +0000, Mike Evans wrote: >> On Sunday February 21 2010 17:22:59 Donald Allen wrote: >> > On Sat, Feb 20, 2010 at 5:48 PM, <[email protected]> wrote: >> > > A question for you folks -- >> > > Does anyone know how far back a data file must go before the SQL >> > > interface starts truncating data? >> > This sort of implies that the cause of this problem is "how far back" >> > the data file goes. We don't know that-- we don't know what the cause >> > is, as yet. > > It worked just fine for me on a build from SVN on 23 January, loading > initially from a gnucash xml file with 127 accounts, approximately 5300 > transactions and going back over 10 years. I then ran various reports, > played with various features, added new transactions and removed new and > old transactions. Didn't notice anything untowards. > > Other points that may be useful: This file would originally have been > written by probably an early version 2.2 gnucash or maybe even a 2.0 > gnucash (I stopped using gnucash for a few years). It also does not > include scheduled transactions, any business functionality (invoices, > etc), stock account activity, or multi-currency transactions.
The cause of the truncation in my tests is understood. See my email to gnucash-devel and the subsequent thread yesterday, or have a look at the bug report. /Don > > Conrad. > > > _______________________________________________ > gnucash-devel mailing list > [email protected] > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
