[Bug 632166] sql backend silently fails and loses data

Christian Stimming stimming at tuhh.de
Mon Oct 18 13:10:18 EDT 2010

For a bug as grave as this one it is completely ok to break the string  
freeze. You can just go ahead and commit. Thanks!


Zitat von John Ralls <jralls at ceridwen.us>:

> I've been working on  
> https://bugzilla.gnome.org/show_bug.cgi?id=632166 this afternoon. I  
> can reproduce the bug, and I've added (but not yet checked in) a log  
> message with more detail than the g_return_val_if_fail message.  
> There should probably be one for each failure reason.
> But to really address this, we need to pop up a message dialog  
> telling the user that the save as didn't go well and that she can't  
> rely on the saved database. The problem is that that's at least one  
> new string to translate. The choices are to break the string freeze  
> (my preference, because I don't think that we should release 2.4.0  
> with the possibility of screwing up the user's accounts) or take  
> this off the milestone list for 2.4.
> Regards,
> John Ralls
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel

More information about the gnucash-devel mailing list