[Qgis-developer] issues with Polish chars in PostGIS column names

[Steven Mizuno]

Maciej Sieczka wrote:
> 
> When I create a table that has Polish 
> characters in a column name like:
> 
> CREATE TABLE instruments ("gęśle" text);
> 
> psql and PgAdmin can work with it fine. QGIS can't.
> 
> When a column with a Polish char in it's name in a PostGIS layer is 
> present, QGIS can't edit the layer - features and columns are not 
> added/removed when digitizing or editing attributes, although QGIS does 
> not yield any errors. The user is not informed QGIS fails to save 
> changes. I guessed what's going on by the fact the column name was 
> garbled which looked suspicius.
> 
> Is this a bug in QGIS?
> 

Yes, there is a problem with non-ASCII characters in PostGIS layers in QGIS.
There is inconsistent use of character set encodings when sending commands
to/ receiving data from PostgreSQL server. I had noticed this when I was
working on a patch for uppercase handling caused by unquoted identifiers
sent to the server.

I have submitted a patch on bug #964 
(https://trac.osgeo.org/qgis/ticket/964) that fixes such
internationalization issues. I believe that it works properly with all
object identifiers as well as data, but have only tested with a PostgreSQL
server having UTF-8 encoding as its default. Even database names can have
non-ASCII characters.

I have also noticed that many database failures do not provoke any message
boxes.

If you are willing to compile patched source, I would be interested in any
feedback, especially if there is something  related to character sets that
doesn't work.

-- 
View this message in context: http://www.nabble.com/issues-with-Polish-chars-in-PostGIS-column-names-tp15918312p15920379.html
Sent from the qgis-developer mailing list archive at Nabble.com.