GNOME Bugzilla – Bug 616100
Incorrect character set used in MySQL backend
Last modified: 2018-06-29 22:38:00 UTC
(This may be related to #559772, but I'm not sure; the bug description is too vague.) First of all, a big "thank you" to all GnuCash developers. I am especially hyped about the new SQL backend, which opens up a whole new range of possibilites with GnuCash. My problem has to do with how non-ASCII characters are stored in a MySQL backend. It seems like a familiar problem, namely that application (GnuCash) uses UTF-8 internally, while the MySQL connection character set is set to Latin-1. If this is the case, one solution is to execute SET NAMES "utf8"; after connecting to the MySQL backend. I believe the mysql_set_character_set() function may be used to the same effect. Note that this will cause encoding problems for people who upgrade from previous versions of GnuCash.
@Phill: You have committed r19200 regarding this bug. That commit first appeared in GnuCash 2.3.13. Is there a reason this bug is still open ?
In other words, is this still a problem in 2.3.15?
I can confirm that the bug is fixed in GnuCash 2.3.15.
Thanks for your feedback. I'll close the report then.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=616100. Please update any external references or bookmarks.