vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| The following bug has been logged online: Bug reference: 1996 Logged by: Ludmil Tinkov Email address: ludmil@fyrex.com PostgreSQL version: 7.3.2 Operating system: RedHat 9.0 Description: DISTINCT fails with national character varying Details: create table depression(ID int, name national character varying(50)) insert into depression values(1, 'Ана'); insert into depression values(2, 'Ива'); insert into depression values(3, 'Ина'); insert into depression values(4, 'Яна'); select distinct name from depression --the last statement returns only a single row --namely: Ана --it should return 4 rows! ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend |
| ||||
| "Ludmil Tinkov" <ludmil@fyrex.com> writes: > select distinct name from depression > --the last statement returns only a single row > --namely: Ана > --it should return 4 rows! This has been seen to happen when you select a database encoding that does not match the encoding expected by the postmaster's LC_CTYPE locale setting. It's really a bug in the locale definitions, if you ask me, but good luck getting the glibc guys to change those :-(. In the meantime, make sure your locale and encoding agree. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
| Thread Tools | |
| Display Modes | |
|
|