Thanks Michael! That's a good thing to know!
On Thu, Sep 25, 2008 at 3:51 AM, Michael Bayer <[EMAIL PROTECTED]> wrote:
>
>
> On Sep 24, 2008, at 2:34 PM, Wim Verhavert wrote:
>
>>
>> How is this possible? I thought that by saying:
>>
>> properties={'achternaam':entity_tabel.c.naam}
>>
>> you actually rename the column, but it seems it creates another
>> attribute which would lead to unexpected results in my case.
>>
>
> normally this is the case but since your Persoon object inherits from
> Entity, the "naam" attribute is inherited from Entity and is still
> present. The case of a subclass trying to "move" the column which
> is named differently on the base class has not been addressed as of
> yet (which basically means, it doesn't work). It would also be a
> little tricky to make it work within SA since if you set different
> data on Persoon.naam and Persoon.achternaam, that would be kind of
> ambiguous. There's no real way for Persoon to not have "naam" at all
> since its a subclass of Entity and from a Python point of view will
> inherit all attributes.
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" 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/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
