Duncan Hill <[EMAIL PROTECTED]> wrote: > Mysql version: 4.1.1 > Platform: Linux, pre-compiled RPMs from mysql.com > > My problem: > Right now, I use a routine that selects the IDs that haven't been seen, and > promptly does an insert into notifications_seen to flag that it has been > seen. This works fine. The moment I do alter table notifications_seen add > unique unq_notifid_loginid (notifid, notif_loginid), my query starts > returning utter foolishness - basically, no records where there were records. > Why does adding a unique index cause this? (Or have I just found a bug?)
The described behavior doesn't appear with supplied tables on version 4.1.2. Probably it's related to the something that is already fixed. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
