Re: [DB-SIG] Proposed improvements to DBAPI 2.0 Cursor.execute() method.

2006-08-16 Thread Harald Armin Massa
I skimmed them, and in my eyes these changes involve a bit too much magic to be helpfull in the full range of database accesses."Since columns is a sequence, and sequences in SQL are always joined by ,, "That is clearly wrong. With the SQL engine I use (PostgreSQL); there is the data type of "ARRAY

Re: [DB-SIG] Proposed improvements to DBAPI 2.0 Cursor.execute() method.

2006-08-16 Thread M.-A. Lemburg
Harald Armin Massa wrote: > I skimmed them, and in my eyes these changes involve a bit too much > magic to > be helpfull in the full range of database accesses. > > "Since columns is a sequence, and sequences in SQL are always joined by > ,, " > That is clearly wrong. With the SQL engine I use (Po

Re: [DB-SIG] Proposed improvements to DBAPI 2.0 Cursor.execute() method.

2006-08-16 Thread Ian Bicking
> Martin Blais wrote: >> I want to propose a few improvements on the DBAPI 2.0 Cursor.execute() >> method interface. You can find the details of my proposed changes >> here: >> http://furius.ca/pubcode/pub/conf/common/lib/python/dbapiext.html >> >> And a pure-Python preliminary implementation of t

Re: [DB-SIG] Proposed improvements to DBAPI 2.0 Cursor.execute() method.

2006-08-16 Thread M.-A. Lemburg
Ian Bicking wrote: >> Martin Blais wrote: >>> I want to propose a few improvements on the DBAPI 2.0 Cursor.execute() >>> method interface. You can find the details of my proposed changes >>> here: >>> http://furius.ca/pubcode/pub/conf/common/lib/python/dbapiext.html >>> >>> And a pure-Python preli