r17780 - gnucash/trunk/src - Fix Bug 559772 – SQL backend not non-ascii-safe

[Phil Longstaff]

Author: plongstaff
Date: 2008-12-19 22:06:17 -0500 (Fri, 19 Dec 2008)
New Revision: 17780
Trac: http://svn.gnucash.org/trac/changeset/17780

Modified:
   gnucash/trunk/src/backend/dbi/gnc-backend-dbi.c
   gnucash/trunk/src/backend/sql/gnc-backend-sql.c
   gnucash/trunk/src/backend/sql/gnc-backend-sql.h
   gnucash/trunk/src/business/business-core/sql/gnc-address-sql.c
   gnucash/trunk/src/business/business-core/sql/gnc-owner-sql.c
Log:
Fix Bug 559772 – SQL backend not non-ascii-safe

Sqlite3 uses utf8 encoding for all char fields, so it is non-ascii-safe.  
For postgresql, the default encoding can be set on a per-db basis.  
Since the database is not created by gnucash (the tables are, but not 
the database), it is for the user to set utf8 encoding when the database 
is created.  For mysql, a default encoding can be set on a per-db, 
per-table or per-field basis.  Since there are char fields which do not 
need to be utf8 (e.g. guids), encoding is set on a per-field basis.