I'd like to point trac devs and plugin authors to a bug I just posted, for verification if possible, and perhaps a solution if someone has one they use (other than fixing each plugin):
http://trac.edgewall.org/ticket/8575 This issue exists in trac and several plugins at the moment. Any table that has a auto_increment=True field will cause the bug if that table is upgraded as described in the bug. Some problem area's potentially include (haven't examined the code to see if the code actually fixes the sequence during upgrade): trac (ticket and report tables, in fact db19.py is a good example of this issue being caused) discussionplugin tracdownloads tracspamfilter trachoursplugin tracpasteplugin trashtalkplugin ittecoplugin Additionally, plugins habitually forget to call (or sometimes missplace the call) db.commit at the end of create/update. Trac does a rollback when the db is released back to the pool to ensure transactions are completed. At least with default settings in postgres, this is pretty broken. Since these are are such common issues, I'm wondering if there is a way to handle this centrally. Trac itself could call db.commit after a create/upgrade (not really advisable), but the auto_increment issue is probably much harder to handle centrally (if at all). Perhaps someone has a good idea on how (if possible) to centralize this. Shane --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
