There are a number of fields which are “descriptive” in one way or another, such that editing these fields outside Gnucash poses to risk to the integrity of the data. The developers know best which fields these are. A number of users have developed external means of editing databases (and I have done some ad hoc editing myself). It would be useful if the developers could list the database fields that are “safe”. I’m not suggesting this be put in the normal documentation, but that it be available somewhere for those who want to dig for it. -- Peter West [email protected] “After me comes he who is mightier than I, the strap of whose sandals I am not worthy to stoop down and untie.”
> On 8 Dec 2020, at 9:44 am, Adrien Monteleone <[email protected]> > wrote: > > Writing to the db is considered risky at this time. (and not supported) > Reading is fine though. > > Regards, > Adrien > > On 12/7/20 5:21 PM, flywire wrote: >>> * If it's not possible through the GUI, how about via issuing SQL >> *>* statements to a database backend?* >> *Seems reasonable.* > > _______________________________________________ > gnucash-user mailing list > [email protected] > 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. _______________________________________________ gnucash-user mailing list [email protected] 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.
