On Tue, 5 Sep 2006, Cristian Gafton wrote: >> cursor() an extra parameter: "name". If a cursor is named then a server >> side cursor with that name is automatically generated (and destroyed at > > I did not go that rounte because of the potential confusion on named > parameters:
Oops, sorry - you wrote cursor() and I read execute() ;-) Yeah, setting the cursor behavior at its creation time also works. However, asking to name it I think ties the spec a bit too close to the driver details - I can see an app writer wanting somethging like "I don't care, don't suck it all the result sets in the client memory". The itercursor() way has the advantage that can be easily aliased to the standard cursor() method for backends where it doesn't really make sense (sqlite, Oracle, etc). Cristian -- Cristian Gafton rPath, Inc. _______________________________________________ DB-SIG maillist - DB-SIG@python.org http://mail.python.org/mailman/listinfo/db-sig
