On Fri, Jul 9, 2010 at 15:26, Tom Lane <t...@sss.pgh.pa.us> wrote: > Dave Page <dp...@pgadmin.org> writes: >> On Fri, Jul 9, 2010 at 4:03 AM, Craig Ringer >> <cr...@postnewspapers.com.au> wrote: >>> I wonder if there's any way to have the bug report form de-duplicate posts >>> based on similar/identical text in sequential submissions. > >> Not without starting down the path of writing a full blown bug >> tracker. The current form just assigns a number from a sequence and >> then forwards the text to the mailing list. None of the contents are >> stored in the database. > > It seems though that it must be very easy to hit "submit" twice, because > we keep seeing these dups. Is there anything the webpage could do to > discourage that? Maybe take you to a different page after submitting?
The code I have up on the new system will make that a bit better, I think. But the best thing would be to store the contents of a bug report in a table somewhere just to look for duplicates. We can expire it after just a minute or so. That'll catch the *exact* duplicates. It could catch partial ones, too. I'll stick that on the TODO list for the new website ;) -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
