[GNC] GNUCash XML format compatibility

[David Carlson]

According to the developers, the only pre-3.x version of GnuCash that is
expected to read data files that have been touched by a 3.x version is
release 2.6.21, possibly with a suffix depending on the OS it is run in.
When a file is first touched by 3.x there are some unspecified changes that
may be at least partially mentioned in other threads here.  They do not
specify if there are any changes in the database variations, but there
probably are.

David Carlson

On Sun, Feb 9, 2020 at 9:08 PM Wirawan Purwanto <wirawan0 at gmail.com> wrote:

> Hi,
>
> I wonder if anyone has a pointer on the changes in Gnucash XML format
> that can cause incompatibility across program versions. I have a
> scenario where one OS uses Gnucash 2.6.x series whereas the other uses
> 3.5. I am concerned when transporting data file back and forth, if
> there is corruption due to incompatible file format.
>
> In my recent trial to migrate files back and forth between 2.6 and
> 3.5, I noted that data seems to be intact. But in the 2.6 series, the
> "cmdty:space" field has the value of "ISO4217" whereas in 3.5 it was
> "CURRENCY". But I noted that a very old GNUCash version (2.4.10)
> failed to read the dates correctly from the file that was saved by
> 3.5. All dates became "1969-12-31" when read in the 2.4 program.
> Because of this I am not quite sure what is safe to do or not safe.
> Would be nice if there is a prominent / easy-to-find web page which
> tells end-user like me regarding file version incompatibility.
>
> --
> Wirawan Purwanto
>
> ~ https://bfa.org ~
> "Get your own copy of a free study Bible"
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> 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.
>


-- 
David Carlson