Re: [SQLObject] ezSqlObject convenience wrapper

[David M. <da...@re...>]

Brad Bollenbach wrote:
> It doesn't make any sense to create another module for this.

I can't say I agree here.

Wrapper modules are a great way to try out ideas.

If the core package devs happen to like one or more of the ideas, they 
can always merge them in, or give cvs write access to whover wrote the 
wrapper.

And if the core devs don't like the ideas, the wrapper writer gets to 
use the wrapped interface in his/her code regardless.

Nobody loses.

> As well, 
> some of these features don't make sense (e.g. I'm not sure what len() on 
> a table is supposed to tell me

len(sometable) simply returns the number of rows in the table.

> [number of columns perhaps?], but len() 
> on a SelectResults is already done by using the count() method on an 
> instance.)

len(something) is slightly more readable and convenient.

> Just ask Ian for checkin privileges (if you don't already have), write 
> unit tests to demonstrate how you want your new features to work, and 
> add them and the code that passes those tests to SQLObject directly.

I wouldn't presume to ask for the ability to maul someone else's 
codebase when I've just drifted in off the net, I'm not known, and there 
hasn't been time for a trust relationship to develop.

Cheers
David

--

leave this line intact so your email gets through my junk mail filter