Well...I thought that indicated data in the session has changed--even if session.save() hasn't been called.
I was hoping that there was a way to tell if a flush *had* occurred (sometime in the past). I guess I could use a decorator on flush(), right? On Feb 8, 10:43 am, "Jonathan Ellis" <[EMAIL PROTECTED]> wrote: > check session.dirty before calling flush()? > > On 2/7/07, Paul K <[EMAIL PROTECTED]> wrote: > > > > > Is there a way I can tell that SQLAlchemy has flushed data to the > > database sometime within the current session and therefore causing a > > potential change to the database? I have an application that needs to > > provide a sqldump ability, but only if the database has changed. With > > sqlite saving to a file, I can be sure enough using an md5sum--however > > I'd prefer a non-database specific solution. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
