Re: [sqlalchemy] Tracking instance commit status

You may be handle this at the database level using triggers. There are some widely used techniques for emulating a "trigger on commit" for postgres and oracle (which don't have that), and that can be used to toggle a flag on the table. But on most databases, you could also track onto the row

Re: [sqlalchemy] Tracking instance commit status

Dear everyone, On Thu, Aug 11, 2016 at 11:08 AM Gombas, Gabor < gabor.gom...@morganstanley.com> wrote: > Well, it is somewhat similar to my use case: there is a part (kind of a > library) of the application which may load an object or it may > transparently create one if it did not exist before.

Re: [sqlalchemy] Tracking instance commit status

On 08/11/2016 03:30 AM, Wibowo Arindrarto wrote: Dear all, I have a little problem with getting object states that have been flushed but not committed. As far as I understand, SQLAlchemy does not have an official object state corresponding to this. The Session is intended to only be working

Re: [sqlalchemy] Tracking instance commit status

Hi Simon, The purpose was to flag those contained objects. These objects are created by the application's users (both container and contained). The user can either create the contained objects manually and let the application infer the container, or they can also create the containers manually.

Re: [sqlalchemy] Tracking instance commit status

On Thu, Aug 11, 2016 at 8:30 AM, Wibowo Arindrarto wrote: > Dear all, > > I have a little problem with getting object states that have been flushed > but not committed. As far as I understand, SQLAlchemy does not have an > official object state corresponding to this.

[sqlalchemy] Tracking instance commit status

Dear all, I have a little problem with getting object states that have been flushed but not committed. As far as I understand, SQLAlchemy does not have an official object state corresponding to this. However, in my application I need to track such objects. My current approach is to listen to