Jeroen Ruigrok van der Werven wrote: > -On [20071113 18:00], Christian Boos ([EMAIL PROTECTED]) wrote: > >> Likewise, most of the remaining 0.11 tickets have now a patch ready, and >> I'm going to apply them in the coming days if there's no further comment >> on them. >> > > Can anyone with a pgsql instance see if my reported > http://trac.edgewall.org/ticket/6348 also has the same issue there? I only > have SQLite instances at the moment. >
Yeah, it's a "known" issue and there's probably several duplicate tickets. Bottom line is that all backends have different ways to report constraint violations: pysqlite2.dbapi2.IntegrityError: columns username, action are not unique _mysql_exceptions.IntegrityError: (1062, "Duplicate entry 'cboos-TICKET_ADMIN' for key 1") psycopg2.IntegrityError: duplicate key violates unique constraint "permission_pk" What we need is to trap that at the level of each backend and raise a TracIntegrityError instead that we can handle in the upper levels. That's not a blocker for 0.11, though. -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
