I think I was moving too quickly and didn't stop to really read what you wrote. I went on what I thought you said. I'll go back and re-read what you wrote.
Rather than reading those specific tags, how about, for any object, unknown tags are read as slots. The values could either always be stored as strings, or some intelligence could be used (numeric values stored as int or double, "F", "T", "true", "false" stored as boolean, string of 32 hex chars stored as guid). Phil ________________________________ From: Derek Atkins <[email protected]> To: Christian Stimming <[email protected]> Cc: gnucash-devel <[email protected]> Sent: Friday, August 21, 2009 11:51:41 AM Subject: Re: 2.3.4 xml files cannot be opened by 2.2.x anymore (?) (Re: Db structure) Christian Stimming <[email protected]> writes: > The use case for loading a 2.3 or 2.4 file into 2.2 again is rather > common: Someone runs the new version for testing and in order to do > thorough testing he uses his live data, but then for whatever reason > doesn't like the current state of the new version and prefers to > continue his daily work in the previous version. > > Does anyone see the same issues? How are we going to deal with this? IMHO we should leaving in the reading of these new tags but turn off the 'writing' of these tags in 2.3/2.4... Which is what I suggested but Phil ignored me. > Regards, > > Christian -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 [email protected] PGP key available _______________________________________________ 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
