The "problem" is that I don't have any orphaned rows left in the user_group table...
I also feel that this patch seems good but since I cannot reproduce the problem (neither with sqlite nor Postgress) I don't really want to take action without at least someone else reporting the bug. As I stated earlier it may come from the fact that I use sqlalchemy 0.3.6 which may handle the situation better than 0.3.5 and this patch may still be required for 0.3.5 I also feel that as a good practice ON DELETE CASCADE should be specified explicitly even if SA handles the jobs without it :) Regards, Florent. On 4/21/07, Paul Johnston <[EMAIL PROTECTED]> wrote: > > Hi, > > >I cannot reproduce the bug explained in: > >http://trac.turbogears.org/ticket/1364 > > > > > Looking at the model, I'd expect SQLAlchemy to null the foreign keys on > delete, so you would be able to delete users who are in groups, even > without this patch. You will get orphaned rows left in the user_group > table though, so that patch is probably a good idea. > > Paul > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
