On Jan 28, 2011, at 1:07 AM, Geert Janssens wrote: > On Thursday 27 January 2011, John Ralls wrote: >> On Jan 27, 2011, at 2:01 PM, Geert Janssens wrote: >>> On Thursday 27 January 2011, Geert Janssens wrote: >>>> I seem to have some issues with the table versioning that was added >>>> recently. I have an sqlite3 based book and whenever I open it, GnuCash >>>> tells me it's created with an old version and should be upgraded. If I >>>> click ok, the file is being re-saved, but the next time I open the file, >>>> it asks me the same question again. >>>> >>>> I have this with a testfile (from the 2.3.x days) with just one >>>> transaction in it. >>>> >>>> Geert >>> >>> Hmm, it even happens with a completely new file, with only accounts in it >>> (no transactions added yet). >> >> Geert, >> >> What do you see if you run >> SELECT * FROM versions where table_name like "Gnucash%"; >> from the sqlite3 shell? >> >> Regards, >> John Ralls > > sqlite> SELECT * FROM versions where table_name like "Gnucash%"; > Gnucash-Resave|19920 > > I just remembered the discussion some time ago about the choice of the > revision number as table version number. I am building GnuCash from a local > git repo, which I keep synchronized with svn. Perhaps that's the cause ?
Possible, I suppose. What's in src/core-utils/gnc-svninfo.h? Seems just as likely that safe_sync doesn't write the current version number. If you add a transaction after opening does the line Gnucash | 20181 (or whatever version is showing up in gnc-svninfo.h) get added? Regards, John Ralls _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
