yahoo-eng-team team mailing list archive

[ChangBo Guo <guochbo@xxxxxxxxxx>]

Public bug reported:

Within the scope of a single method, keeping all the reads and writes within
the context managed by a single session. In this way, the session's __exit__
handler will take care of calling flush() and commit() for you.
If using this approach, you should not explicitly call flush() or commit().
See http://stackoverflow.com/questions/4201455/sqlalchemy-whats-the-difference-between-flush-and-commit

** Affects: keystone
     Importance: Undecided
     Assignee: ChangBo Guo (guochbo)
         Status: In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1258044

Title:
  Don't need session.flush in context managed by session in sqlalchemy

Status in OpenStack Identity (Keystone):
  In Progress

Bug description:
  Within the scope of a single method, keeping all the reads and writes within
  the context managed by a single session. In this way, the session's __exit__
  handler will take care of calling flush() and commit() for you.
  If using this approach, you should not explicitly call flush() or commit().
  See http://stackoverflow.com/questions/4201455/sqlalchemy-whats-the-difference-between-flush-and-commit

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1258044/+subscriptions