Re: [SQLObject] Namespace pollution

[Ian B. <ia...@co...>]

On Sun, 2003-06-01 at 02:35, Edmund Lian wrote:
> The way SO does things is quite nice. I do like the use of metaclasses 
> to add in new methods as a result of joins. But, there needs to be a way 
> to inspect the objects to see what methods and attributes have been 
> automagically added, I think.
> 
> I'm just speculating--because I haven't had the problem yet--that it 
> could be quite easy to accidentally over-ride an automagically added 
> method/attribute. Particularly if you've got a lot of classes, or wrote 
> them a long time ago, or somebody else wrote them. In which case, it 
> isn't at all obvious the methods/attributes of each object are.

Hmm... well, there are some private variables that hold information,
like _SO_columnDict, in addition to the public _columns and _joins (poor
naming aside).  There's nothing very public at this point.  Like with
most of these things, I don't want to commit to anything until I know
how it's *really* going to be used -- mostly to design the interface
more appropriately.

  Ian