[sqlalchemy] Re: Versioning and Foreign Keys

2011-09-19 Thread JPLaverdure
Oops, above references to versioned_meta should read history_meta. Sorry -- You received this message because you are subscribed to the Google Groups sqlalchemy group. To view this discussion on the web visit https://groups.google.com/d/msg/sqlalchemy/-/0ZtFX94qz_wJ. To post to this group,

Re: [sqlalchemy] Re: Versioning and multi-level inheritance

2011-08-31 Thread Michael Bayer
version is only on your Container table since it will always have a row corresponding to each Box row, so box.version is not necessary. You can change this by changing: if not super_history_mapper: cls.version = Column('version', Integer, default=1, nullable=False) to:

Re: [sqlalchemy] Re: Versioning and multi-level inheritance

2011-08-31 Thread JPLaverdure
Hi Michael, Thank you for your reply. Unfortunately, the mistake was all mine... At some point (and for an obscure reason...), I had stopped using the VersionedListener so changes were no longer registering in the DB :-/ So sorry ! JP -- You received this message because you are subscribed

Re: [sqlalchemy] Re: Versioning and multi-level inheritance

2011-08-31 Thread Jean-Philippe Laverdure
Hi Michael, Thank you for your reply. Unfortunately, the mistake was all mine... At some point (and for an obscure reason...), I had stopped using the VersionedListener so changes were no longer registering in the DB :-/ So sorry ! JP On Wed, Aug 31, 2011 at 12:23 PM, Michael Bayer

[sqlalchemy] Re: versioning and complex collection

2011-02-24 Thread Tim-Erwin
Michael, thanks a lot for your thorough and informative reply. I'll take my time and think about all that / try out stuff. Just so you know why it's taking so long till I answer again... Tim -- You received this message because you are subscribed to the Google Groups sqlalchemy group. To post

[sqlalchemy] Re: versioning when updating a relationship

2010-12-22 Thread Andronikos Nedos
The versioning example appears to be cautious about determining if there was a net change present.    The good news is that we don't actually need the new value of customer_ref when we create the historical entry, we need the current entry, which should be present in the object's dict.  

[sqlalchemy] Re: Versioning

2008-09-12 Thread Diez B. Roggisch
Sam schrieb: One of the things I really liked about sqlobject was its versioning plug-in. ( http://www.sqlobject.org/Versioning.html ) Is there anything similar for sqlalchemy? A google search turned up versioned ( http://elixir.ematia.de/apidocs/elixir.ext.versioned.html ) This is a

[sqlalchemy] Re: Versioning

2008-09-12 Thread az
On Friday 12 September 2008 05:37:35 Sam wrote: One of the things I really liked about sqlobject was its versioning plug-in. ( http://www.sqlobject.org/Versioning.html ) Is there anything similar for sqlalchemy? A google search turned up versioned (

[sqlalchemy] Re: Versioning

2008-09-12 Thread Gaetan de Menten
On Fri, Sep 12, 2008 at 4:37 AM, Sam [EMAIL PROTECTED] wrote: One of the things I really liked about sqlobject was its versioning plug-in. ( http://www.sqlobject.org/Versioning.html ) Is there anything similar for sqlalchemy? A google search turned up versioned (