[DB-SIG] paramstyles, again (and now voting)

Carl Karsten carl at personnelware.com
Thu Jun 21 05:59:18 CEST 2007


Carsten Haese wrote:
> On Wed, 2007-06-20 at 16:59 -0500, Carl Karsten wrote:
>> M.-A. Lemburg wrote:
>>  > How about making both qmark and named the minimum required
>>  > parameter styles ?!
>>  >
>>
>> Forget minimum.
>> Make qmark and named requried.
>> Make paramstyle something that is set/passed in as part of the init, and is
>> ReadOnly after that.   It should default to the same thing in all implementations.
>>
>> I think we can make it super simple, and it will be way better than the current
>> implementation.
>>
>> For backwards compatibility,  It should be pretty easy to wrap all the v3
>> modules in a v2 conversion layer that will add the extra 'features' like pyformat.
> 
> And how is bolting on a conversion layer "super simple" compared to not
> breaking backwards compatibility in the first place?
> 

"super simple" would be the new api.   pretty easy is the wrapper for backwards 
computability.

As complex as that set would be, it wouldn't be much worse than the current mess.

"worse" would be a small price to pay for a much better API.

Carl K


More information about the DB-SIG mailing list