Re: PyDO suggestions/comments

Jacob Smullyan wrote:
> setLogLevel is named that way because of the assumption
> that it will be imported from the package, not the log submodule.

Makes sense.

>>Could getUnique be renamed simply get for convenience?
> 
>  
> I wouldn't care for that, because get() is already a dict method and I
> don't like to use it for other things.  If you want it, you can alias
> getUnique in a subclass.

How about getOne, then?  Or fetch, or load?

Or...  what about the SQLObject approach, where the constructor performs the 
equivalent of getUnique and then there is a fetch/getSome method for multiple 
rows?

This must seem like nitpicking, but first impressions count a lot.  And I plan 
to write a lot of PyDO code so I'd like to make my life easier, too. :)

-Jonathan


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click