>From: Andy Todd [mailto:[EMAIL PROTECTED] >Dittmar, Daniel wrote: >> But how should a module support multiple notations? >> - by tokenizing any SQL statement to check which paramstyle was used >> - by having an option on the connection or the cursor >> - by having an additional method which requires qmark >placeholders (this >> one would be backwards compatible) >> >As paramstyle is currently an attribute of the module perhaps it could >be inherited by the connection. That way the user (if the >module allows) >could set the paramstyle on their connection to one of the available
Sounds sensible to me. But I remember that I made a similar proposal a while back. And someone argued that there were some applications where 'creating the connection' and 'using execute ()' were in completely different layers. I don't know how valid this argument still is (or ever was). >options. If the module only supports a single paramstyle then changing >the attribute on the connection would have no effect. An exception perhaps? Daniel -- Daniel Dittmar SAP Labs Berlin [EMAIL PROTECTED] _______________________________________________ DB-SIG maillist - DB-SIG@python.org http://mail.python.org/mailman/listinfo/db-sig
