Florent Aide wrote: > 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
Florent was right, my problem was caused by an old SQLAlchemy version. The current 0.3.6 version automagically cascades deletes (and I assume updates as well) to the intermediate table if you use the "secondary" option in the mapper. So the explicit "on delete" is not necessary, but useful if you edit the user tables directly without SQLAlchemy (for instance, I like to use pgAdmin for this on PostgreSQL). -- Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
