On Jul 22, 2013, at 10:22 AM, Michel Albert <exh...@gmail.com> wrote:
> Hi, > > > I realised that SA adds an instance to the session as soon as I instantiate > it. How/Where can I disable this? > > For example: currently I have this behaviour: > > >>> session = get_session() > >>> my_user = User(email='f...@example.com') > >>> len(session.query(User)) > 1 this is not SQLAlchemy's behavior, it is typically the work of an extension such as Flask-SQLAlchemy or Elixir (and the configuration would lie with those tools). SQLAlchemy by itself would have no way of knowing that your User class has any association with a Session somewhere. The one exception to this is if you are associating two objects together, where one is already in a session, such as: user = User(some_parent_object=my_object_already_in_session) in that case, the User might be *cascaded* into the Session that the other object is already part of. This is a different issue with a different way of configuring it. -- 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 sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/groups/opt_out.
