gladly http://www.sqlalchemy.org/trac/ticket/858
On Nov 8, 10:19 am, Michael Bayer <[EMAIL PROTECTED]> wrote: > Hi Chris - > > can you please assemble a fully reproducing test case and create a new > ticket in trac ? I can vaguely think of why the add_column() youre > doing there might not work correctly and its probably not that hard of > a fix, but we're a little overloaded with issues/enhancements this > week and having a short test case with which to assemble a unit test > would be helpful. > > thanks, > > - mike > > On Nov 7, 2007, at 11:31 PM, Chris M wrote: > > > > > I haven't tested with the trunk yet, but at least in 0.4.0 there are > > some inconsistencies with how Query.add_column works. Assuming I have > > instrumented class Class: > > > Class.query.add_column(Class.some_data) # The added column is > > completely ignored > > Class.query.add_column(Class.c.some_data) # ... but this works? > > > The odd part is that in the first example, there is no error message > > or anything, just a complete ignore. I was surprised by this behavior > > - I'm not required to use the .c. prefix on most things in SQLAlchemy, > > and where I can't I at least get some sort of error message. It took > > me a few tries to actually figure out what was going on and this isn't > > mentioned anywhere in the documentation, so I figured I'd bring it up. > > I figure others will be confused as well since > > select([Class.some_data]) works fine. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
