BUG #1698: Different behavior in UNIQUE and DISTINCT
От | Mauro Delfino |
---|---|
Тема | BUG #1698: Different behavior in UNIQUE and DISTINCT |
Дата | |
Msg-id | 20050602192207.95EE1F0AC7@svr2.postgresql.org обсуждение исходный текст |
Ответы |
Re: BUG #1698: Different behavior in UNIQUE and DISTINCT
|
Список | pgsql-bugs |
The following bug has been logged online: Bug reference: 1698 Logged by: Mauro Delfino Email address: maurodelfino@gmail.com PostgreSQL version: 7.4.6 and 8.0.3 Operating system: Debian and Windows 2003 Server Description: Different behavior in UNIQUE and DISTINCT Details: I have the these two tables: CREATE TABLE table_one ( field1 VARCHAR(255) ); CREATE TABLE table_two ( field1 VARCHAR(255) UNIQUE ); table_one has 500k records. I certify that all strings are distinct with this query: SELECT DISTINCT field1 FROM table_one; The query results 500k rows. But if I try to insert the records of table_one into table_two with the following command: INSERT INTO table_two (field1) (SELECT field1 FROM table_one); This error occurs: ERROR: duplicate key violates unique constraint "table_two_field1_key" What happened? DISTINC and UNIQUE have different algorithms to determine when two strings are equal? PS: I've tested this situation on PG 7.4.4 on Debian and 8.0.3 on Windows 2003 Server. PS2: Database encoding is LATIN1 Thanks in advance.
В списке pgsql-bugs по дате отправления: