SQL Version

[Derek Atkins]

Geert Janssens <janssens-geert at telenet.be> writes:

> On Friday 28 January 2011, John Ralls wrote:
>> > 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?
>> 
> $ cat BuildWebkitDbg/src/core-utils/gnc-svninfo.h 
> /* Autogenerated. Do not change. */
> #define GNUCASH_SVN_REV "f9cd753+"
>
> That matches the git hash for the commit used build GnuCash.
>
>> 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?
>> 
> No, it's still 
> Gnucash-Resave|19920

And already we hit the "version is not a monitonically increasing
number" issue.   :-D

Seriously, we should just have a "schema version" defined in a header
file somewhere and just "remember" to change it whenever we make schema
changes.  The 'gnucash version' (and revision string) should only be
there for informational purposes.

>> Regards,
>> John Ralls
>
> Geert

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available