[TinyOWS-dev] Default database encoding

Carlos Ruiz boolean10001 at yahoo.com
Wed Feb 16 10:50:56 EST 2011


No, the XML encoding works fine, so you don't have to restore the wfs_x files. 
The PostgreSQL database 

encoding is set after the connection opening with the PQsetClientEncoding 

The recent patch only affects the ows.h, ows.c and ows_config.c files to support 
the db_encoding 

attribute of the tinyows element in the config.xml file:


To add thedb_encoding buffer to the ows struct and to define the 
DEFAULT_XML_ENCODING and the DEFAULT_DB_ENCODING constants (as a best practice).


To set the PostgreSQL database encoding with the db_encoding buffer contents and 
to dump or free this 



To read the db_config attribute from the config.xml file if exists or to set it 

if it doesn't exist.

I hope this clarify more of the recent patch (diff_2011_02_15.patch) intends.


IC Carlos Ruiz

From: Olivier Courtin <olivier.courtin at gmail.com>
To: TinyOWS developers discuss list <tinyows-dev at lists.maptools.org>
Sent: Tue, February 15, 2011 2:44:45 PM
Subject: Re: [TinyOWS-dev] Default database encoding

On Feb 15, 2011, at 6:27 PM, Carlos Ruiz wrote:


> It seems that it is necessarely to specify a default PostgreSQL  
> database encoding after all. This patch is the
> same as the last one (2011_02_11.patch) + the default database  
> encoding (UTF8) to match the XML one.

Ok so i guess i have to restore the encoding stuff in wfs_transaction,  
wfs_get_feature... files ?

TinyOWS-dev mailing list
TinyOWS-dev at lists.maptools.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.maptools.org/pipermail/tinyows-dev/attachments/20110216/599e4f3b/attachment.htm 

More information about the TinyOWS-dev mailing list