Re: UTF-8 encoding problem w/ libpq

From: "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu>
To: Martin Schäfer <Martin(dot)Schaefer(at)cadcorp(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: UTF-8 encoding problem w/ libpq
Date: 2013-06-03 15:27:51
Message-ID: 20130603152751.GH2892@aart.rice.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 03, 2013 at 04:09:29PM +0100, Martin Schäfer wrote:
>
> > > If I change the strCreate query and add double quotes around the column
> > name, then the problem disappears. But the original name is already in
> > lowercase, so I think it should also work without quoting the column name.
> > > Am I missing some setup in either the database or in the use of libpq?
> > >
> > > I’m using PostgreSQL 9.2.1, compiled by Visual C++ build 1600, 64-bit
> > >
> > > The database uses:
> > > ENCODING = 'UTF8'
> > > LC_COLLATE = 'English_United Kingdom.1252'
> > > LC_CTYPE = 'English_United Kingdom.1252'
> > >
> > > Thanks for any help,
> > >
> > > Martin
> > >
> >
> > Hi Martin,
> >
> > If you do not want the lowercase behavior, you must put double-quotes
> > around the column name per the documentation:
> >
> > http://www.postgresql.org/docs/9.2/interactive/sql-syntax-
> > lexical.html#SQL-SYNTAX-IDENTIFIERS
> >
> > section 4.1.1.
> >
> > Regards,
> > Ken
>
> The original name 'id_äß' is already in lowercase. The backend should leave it unchanged IMO.
>
> Regards,
> Martin
>

Only in utf-8 which needs to be double-quoted for a column name as you have
seen, otherwise the value will be lowercased per byte.

Regards,
Ken

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2013-06-03 15:43:10 Re: Implicit rule created for materialized views
Previous Message Alvaro Herrera 2013-06-03 15:10:52 Re: Running pgindent