On 10/25/07, Isaac Csandl <[EMAIL PROTECTED]> wrote: > > > > On Oct 24, 2:39 pm, Jonathan LaCour <[EMAIL PROTECTED]> > wrote: > > Isaac Csandl wrote: > > > Bug: You can't flush any object that has any fields with > > > deferred=True. > > > > > Filed as ticket #17: > > > > >http://elixir.ematia.de/trac/ticket/17 > > > > Thanks for the report. I left a comment on the ticket. It looks like > > the bug is actually in SQLAlchemy 0.4.0. I'll report it over on the > > SQLAlchemy bug tracker. > > > > When I revert to Elixir r220 but keep SA at 0.4.0, then deferred works > as expected. I haven't looked to see if Elixir is adding the property > differently in r220, so this observation may be irrelevant.
It does add those kind of properties differently in the latest trunk than in r220: now all properties are added at the same point in time. Previously, normal properties were added after the mapper via add_property and deferred properties were specifically taken care of at a different time. Since, I've now generalized the behavior, all properties are added at the same time (which is a good thing). The bad side of it is that it might be better to define properties at mapper creation time, to avoid such bugs for example. I honestly don't remember why I added properties after the mapper. I suspect it was because of an internal limitation of Elixir we had before I merge the "autosetup"/autodelay thing. I'll have a look to see if I can change that easily... Thanks for the catch btw! -- Gaëtan de Menten http://openhex.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SQLElixir" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlelixir?hl=en -~----------~----~----~----~------~----~------~--~---
