Re: GC 2.6.99 built from git rev d96bb3ebd+ corrupts MySQL db
> On Sep 6, 2017, at 2:59 PM, Art via gnucash-user > wrote: > > It reports that it's corrupt when I attempt to save a valid XML db to MySQL > and in fact it is, as verfied through the MySQL workbench. > However, I just downloaded 2.6.17 source from the GC web site and it works > perfectly! > Somehow git cloning 2.6.99 is not the right thing to do. > Oops. > Thank you, though I was looking forward to some down and dirty source code > and API troubleshooting. Please go ahead and do the down-and-dirty troubleshooting, just not on your production database! The SQL backend has been substantially rewritten for the next major release and needs thorough testing. Since there are foo_back tables it would seem that a safe_save is getting interrupted. Regards, John Ralls ___ gnucash-user mailing list gnucash-user@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: Re: GC 2.6.99 built from git rev d96bb3ebd+ corrupts MySQL db
It reports that it's corrupt when I attempt to save a valid XML db to MySQL and in fact it is, as verfied through the MySQL workbench. However, I just downloaded 2.6.17 source from the GC web site and it works perfectly! Somehow git cloning 2.6.99 is not the right thing to do. Oops. Thank you, though I was looking forward to some down and dirty source code and API troubleshooting. - Art On Wednesday, September 6, 2017, 5:11:45 PM EDT, Colin Law wrote: On 6 September 2017 at 22:04, Art via gnucash-user wrote: > ... > ...So I assumed it should be working, but as soon as I do a file open on my > db, I get a pop-up, The server at URL mysql://root@localhost/gc2017 > experienced an error or encountered bad or corrupt data. > When I look at the db with the workbench I notice that the "accounts" table > has been backed up to "accounts_back" and the "accounts" table now has two > records with field name "Root Account", account_type="ROOT" with a guid > field. At this point, the db is corrupt. I don't want to revert to GC 2.6.15 > if I can fix this. I want to keep using MySQL and I can't just save an XML to > MySQL because it also reports that the db is corrupt. So, I must be making a > fundamental mistake or series thereof because I haven't heard anyone else > complain about any issues with the MySQL backend. Maybe I'm pulling the wrong > version? I am only using git at this point to get the source code. What happens if you save to a mysql db of a different name (or delete the current db first)? Colin ___ gnucash-user mailing list gnucash-user@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: GC 2.6.99 built from git rev d96bb3ebd+ corrupts MySQL db
On 6 September 2017 at 22:04, Art via gnucash-user wrote: > ... > ...So I assumed it should be working, but as soon as I do a file open on my > db, I get a pop-up, The server at URL mysql://root@localhost/gc2017 > experienced an error or encountered bad or corrupt data. > When I look at the db with the workbench I notice that the "accounts" table > has been backed up to "accounts_back" and the "accounts" table now has two > records with field name "Root Account", account_type="ROOT" with a guid > field. At this point, the db is corrupt. I don't want to revert to GC 2.6.15 > if I can fix this. I want to keep using MySQL and I can't just save an XML to > MySQL because it also reports that the db is corrupt. So, I must be making a > fundamental mistake or series thereof because I haven't heard anyone else > complain about any issues with the MySQL backend. Maybe I'm pulling the wrong > version? I am only using git at this point to get the source code. What happens if you save to a mysql db of a different name (or delete the current db first)? Colin ___ gnucash-user mailing list gnucash-user@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
