I've been running GnuCash for years with a MySQL DB as the backend. I host the DB in GCP, so the app is a frontend, and I can run it on any computer.
For performance and offline access reasons, I've been considering using SQLite3 locally instead. I would back up the .gnucash file regularly. I already do this for smaller entities with tarball backup in Google Drive. But I would love to keep a MySQL copy somewhat up to date, maybe weekly during busy periods or monthly after close. Would a simple "Save as..." to the MySQL endpoint, as-needed, work? Would it automatically overwrite everything that's already there? Or would it know what changed since the last save? Or would I have to start from a clean DB for every save? I have custom reporting I do directly from the DB, and would like to keep this option open. Unfortunately, I don't know much about the different backends or how they open and save. Regards, -- Charles Gagnon charlesg at unixrealm.com _______________________________________________ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: 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.
