The fix for this is spreading out into some deeper code changes, all for the better but it's tipping past the point I'd want to put this into 0.6.9, so for the moment I'm going to keep this in the 0.7 series.
On Aug 18, 2011, at 4:56 PM, Michael Bayer wrote: > > On Aug 18, 2011, at 4:24 PM, Michael Bayer wrote: > >> >> However, the original select() is still wrong. _from_objects gave it the >> wrong data, period. How to guard against this issue, a potentially >> expensive reorg of Select internals. As well as future issues of this >> sort, using Column objects which generates cached state, then mutating the >> Column. > > this is ticket 2261 http://www.sqlalchemy.org/trac/ticket/2261 , a patch > fixing the issue is present there to defer the generation of Select._froms as > well as warn within Column when you attach to a table post-maturely, the > patch will be available in release 0.7.3 as well as 0.6.9. > > > -- > 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 > sqlalchemy+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sqlalchemy?hl=en. > -- 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 sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
