After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 562848 - it is unclear how to go back to xml backend from sql backend
it is unclear how to go back to xml backend from sql backend
Status: RESOLVED FIXED
Product: GnuCash
Classification: Other
Component: Backend - SQL
git-master
Other Linux
: Normal enhancement
: ---
Assigned To: Chris Shoemaker
Chris Shoemaker
: 562841 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-12-01 10:32 UTC by Rolf Leggewie
Modified: 2018-06-29 22:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Rolf Leggewie 2008-12-01 10:32:58 UTC
Hi,

this issue should probably be fixed alongside bug 562841.

There is no obvious way to go back from an SQL backend to an XML backend.  In fact, I thought "Save as" would do that, but it defaulted to sqlite for file format.  Overwriting an XML file will get gnucash to export SQL to XML, though, as I found out later.

I think the best way would be an option to explicitly specify the backend in the "Save As" dialog.

Regards

Rolf
Comment 1 Christian Stimming 2008-12-01 12:50:25 UTC
*** Bug 562841 has been marked as a duplicate of this bug. ***
Comment 2 Christian Stimming 2008-12-01 12:50:59 UTC
*How* should it be integrated? How should the GUI look like instead?

The save dialog is the stock Gtk dialog where we can't easily change the GUI. Feel free to submit a patch; otherwise this won't happen.
Comment 3 Phil Longstaff 2008-12-22 17:30:44 UTC
We could use the Gtk save widget and embed it in a dialog along with the db connection information.  This could also allow a selection between sqlite3 and xml storage.  The same thing would be done for the open dialog.
Comment 4 Rolf Leggewie 2009-02-11 09:36:17 UTC
I am increasing the importance for this to critical because of a potential for data loss

Start up a dbi-enabled gnucash from svn.  Try to save your data back to XML by overwriting an old xml file you have for the purpose.  You'll be warned that the file exists and if you want to do that. Everything will seem smooth sailing.  But when you close and reopen that XML file, you'll see that while the account structure apparently has survived intact, your splits did not.  All accounts are at 0.

Somebody please verify.
Comment 5 Andreas Köhler 2009-02-14 16:39:51 UTC
(In reply to comment #4)
> I am increasing the importance for this to critical because of a potential for
> data loss
> 
> Start up a dbi-enabled gnucash from svn.  Try to save your data back to XML by
> overwriting an old xml file you have for the purpose.  You'll be warned that
> the file exists and if you want to do that. Everything will seem smooth
> sailing.  But when you close and reopen that XML file, you'll see that while
> the account structure apparently has survived intact, your splits did not.  All
> accounts are at 0.
> 
> Somebody please verify.

I cannot reproduce that with r17897.
Also, please open a separate bug if saving a copy of an sqlite file fails in certain circumstances.

Lowering this one again.
Comment 6 Phil Longstaff 2009-03-14 14:48:21 UTC
Implemented in trunk r17989
Comment 7 John Ralls 2018-06-29 22:13:18 UTC
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=562848. Please update any external references or bookmarks.