3 ms·
Is the MySQL backend option fully functional now? I need to be able to code sql reports for my small business, or it's a no-go for us.
by koheripbal 4y ago
Is the MySQL backend option fully functional now? I need to be able to code sql reports for my small business, or it's a no-go for us.
- memling 4y ago> Is the MySQL backend option fully functional now? Out of curiosity, was there anything about it that wasn't working? When I got married I moved away from GNUCash because the interface was too intimidating...but I had been using the MySQL backend for a few years by then? and I don't recall any issues with it.
- NoboruWataya 4y agoI have no issues with it, though the website still has this warning: > Note this feature is considered experimental. It works for most of the common use cases but some corner cases have been reported to result in data loss. The GnuCash developers fix each issue as it gets reported. There is however no full test coverage so there may still be scenarios left that result in data loss.
- koheripbal 4y agoAnyone serious about their business will see this warning as a deal-breaker. Running a business is hard enough - I cannot imagine debugging my accounting tool.
- NoboruWataya 4y agoI should clarify that the warning applies specifically to the SQL storage format. I'm not aware of any data loss issues using the default XML format. Agree that as a business you would not want to take any chances. For my personal use I use SQL because that means I can use the piecash[1] library to interact with my financial data without relying on the official Python bindings (which aren't great to use). [1] https://pypi.org/project/piecash/ https://pypi.org/project/piecash/
- dorfsmay 4y agoThe SQLite backend works fine. Could you use that for your reports?