On Jul 22, 1:33 pm, Michael Bayer <[EMAIL PROTECTED]> wrote:
> On Jul 21, 2008, at 9:45 PM, huy do wrote:
>
>
>
> > Because a mapped class can have an arbitary select as it's source i.e
> > columns from any table theoretically, it would still be nice to know
> > exactly which columns were used to map the properties of a given
> > class. The ".c" on the model class use to give us the metadata (i.e
> > either the select or table aka relation) which was used to populate
> > the class. Can we get an extension to get this feature back (please) ?
>
> If you just want the Table, its just
> class_mapper(class).mapped_table. Theres lots of ways to build your
> own ".c." class attirbute and such, including:
>
> MyClass.c = class_mapper(MyClass).columns
cool.
>
> the ".c." really had to be removed....its entirely different now if
> you say query.filter(MyClass.c.foo=='bar') in 0.5 since no adaptation
> will take place.
I don't mind getting rid of MyClass.c.foo == 'bar' with MyClass.foo
== 'bar',
but is it possible to add MyClass.foo.c to get at the metadata behind
the column itself.
Thanks
huy
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
