RE: [SQLObject] proxy attributes

[<jws...@ra...>]

>> No, customers = accounts and buyers = people. Inheritance is one way of 
>> looking at it, though. I will investigate that.
>
>perhaps not.  (i do not think that you mean "account is a man" 
>inheritance, do you?)  in our application, we had an object-oriented 

Actually, I do.

Since python has multiple inheritance, you can see a parallel between joins
and inheritance. Think of it like a mixin class. Not "account IS a man", 
account has the properties of a man. Since we are talking about databases,
these are attribute-only classes. No methods are inherited, since none 
exist.

In the two parallel universes-

The account table joins to the buyers table, and the buyers attributes are 
accquired by the account.

An account object inherits from the buyer class and merges the buyer 
attributes into itself.

I will investigate the inheritance code. Perhaps that would more appropriate
if there is interest in that approach.