[GNC] Going Back to Go Forward?

Michael mjchurchil at aol.com
Mon Aug 6 10:26:47 EDT 2018


It is my understanding that 2.6.21 is the only 2.6.x that is compatible 
with the 3.2 data structure.  I have used 2.6.21 successfully with 3.2 
data, but older 2.6.x report that they are not compatible.  I believe 
that is true of xml and sql databases.  Mike

On Mon, Aug 6, 2018 at 4:17 AM, Thomas Forrester 
<tlforrester at gmail.com> wrote:
> On a Windows computer, I upgraded to 3.2 from 2.6.20 I think it was 
> back
> when I first noticed version 3 had been released.  Took me till 3.2 to
> notice, but I think it was within a few days of the 3.2 release
> 
> Having now used 3.2 for a short while, I'm wondering if there's any 
> issue
> with going back to 2.6.x?  In other words, are there any underlying 
> data
> structure changes, or other file changes, that would make this a huge
> mistake?  I am using the MySQL database backend.
> 
> I just feel at this point that, if I can't further edit anything after
> pasting something in from the clipboard, that it may be a better idea 
> to go
> back so I can go forward.
> _______________________________________________
> 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.


More information about the gnucash-user mailing list