"David Johnston" <polobo(at)yahoo(dot)com> writes:
> PostgreSQL 9.1beta1, compiled by Visual C++ build 1500, 64-bit (EnterpriseDB
> Install Executable)
> CREATE DATABASE betatest
> TEMPLATE template0
> ENCODING 'UTF8'
> LC_COLLATE 'C'
> LC_CTYPE 'C';
> CREATE DOMAIN idcode AS text
> NOT NULL CHECK (VALUE ~* '^\w[-:\w]*$')
> SELECT 'AAAAAaaaaa'::idcode; // -> SQL Error: ERROR: value for domain
> idcode violates check constraint "idcode_check" (note the accented e
> between all the As)
AFAICS that's correct behavior. C locale should not think that is
> This is running just fine against a 9.0 install on the same machine.
We made some strides towards getting locale-sensitive stuff to work as
it "should" in 9.1. In particular, platform-specific creative
interpretations of what C locale means shouldn't happen anymore ...
regards, tom lane
In response to
pgsql-general by date
|Next:||From: Tom Lane||Date: 2011-05-31 03:09:45|
|Subject: Re: Function Column Expansion Causes Inserts To Fail |
|Previous:||From: Tom Lane||Date: 2011-05-31 02:14:08|
|Subject: Re: UTC4115FATAL: the database system is in recovery mode |