Search Postgresql Archives

Re: [HACKERS] Invalid unicode in COPY problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"John Hansen" <john@xxxxxxxxxxxxxx> writes:
> Tatsuo Ishii wrote:
>> We have developed patches which relaxes the character 
>> validation so that PostgreSQL accepts invalid characters.

> That is just plain 100% wrong!!

That was my first reaction too.  Why would this be a good idea?
If someone does want an encoding-agnostic database, they can
set it as SQL_ASCII.

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux