Hey Manilo, My feeling is that this is out of the scope of the SQLAlchemy project. It should support the official workings for each database package, not extend it. It is pretty easy to implement this yourself and use SQLAlchemy on top of that (I use a lot of triggers in my app). There may be something to say for pythonizing triggers so they become database agnostic, but I am not even sure if that is possible given all the different triggers different databases can have.
What do you mean by 'unstable internals' in SQLAlchemy? Kindest regards, Koen Bok On Jan 28, 12:03 pm, Manlio Perillo <[EMAIL PROTECTED]> wrote: > Hi. > > In this wiki page:http://www.sqlite.org/cvstrac/wiki?p=ForeignKeyTriggers > > there is a recipe on how to add basic foreign key support to SQLite > using triggers. > > Is it possible to implement this recipe in SQLAlchemy? > > Some time ago I have tried to implement it, by adding support for > triggers in SQLAlchemy (so that they can be automatically > created/dropped) but I have abandoned the project because the internals > of SQLAlchemy are unstable. > > Thanks Manlio Perillo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---