hello, On 05/25/15 16:51, [email protected] wrote: > I know there is no absolute solution for my question. I just want to > hear your suggestions and how you do this in your practice. > > In which layer of the MVC-pattern are all the SQLAlchemy objects > located? > > There should be a Session for each action. But who does this action? > The controller? > In my current solution I have controllers holding a Session object. The > controller does the add(), commit(), rollback() stuff.
same here but before passing the model instance from controller to view, all instances are detached from session (via expunge()). this 1) prevents a lot of unexpected db queries. 2) lets you recycle db connections as soon as possible. > The models can be all declaraive_base() derived classes. > > How do you realize this? > have a look at http://spyne.io e.g. http://spyne.io/#s=sql&ser=SqlOtm&show=Schema -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
