Some time back, Costin Grigoras <[EMAIL PROTECTED]> wrote:
> how could duplicate records appear when the unique index existed ?
After re-reading this old bug report, I realized that all of the methods
you were applying would make use of the index itself to search for
duplicates --- the count(*) su
Costin Grigoras <[EMAIL PROTECTED]> writes:
> how could duplicate records appear when the unique index existed ?
Good question. I have a sneaking suspicion that your trigger might be a
contributing factor, but I'm not sure how. Can you provide a
self-contained test sequence to reproduce the prob
hello,
i encountered the following problem :
mail=# \d user_preferences
Table "public.user_preferences"
Column | Type | Modifiers
--+-+---
up_uid | integer |
up_id| integer |
up_value | text|
Indexes:
"user_preferences_id_uid_uidx" unique, btree (up
