Koen Bok ha scritto: > 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.
Right, this should not be part of SQLAlchemy "core", but maybe in a contrib package? Nobody else has written a small function for this "easy" job? > 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. > Not sure, but the generic syntax is quite standard. The only problem is the trigger "action". > What do you mean by 'unstable internals' in SQLAlchemy? > Unstable internal API. > Kindest regards, > > Koen Bok > 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 -~----------~----~----~----~------~----~------~--~---
