>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 hav
>On Wed, 2006-04-19 at 08:24, M.-A. Lemburg wrote:
>> I've found the qmark style to be sufficient for everything
This is more about convenience (same as Python positional arguments vs.
keyword arguments). Celko's book on SQL tree structures is full of
examples using :names, with the same name appe
rough keyword arguments could have the advantage that it
is easier to add some property values at runtime, for example, if the
password must be entered interactively. Inserting it into a URI would
require some knowledge about the URI format (which is supposed to be
database specific).
Daniel Dittmar
--
product name is generally
preferable (and seemed to be the consent so far). With the JDBC scheme,
all relevant drivers have to be loaded into memory first, the diver
manager then asks each if the driver would accept a specific URI.
c) Should username and password be used similar to other protocols
>> An alternative would be to always use uri_connect. In
>addition, a set of
>> modules is provided that implements this uri translation for older
>> drivers. The user would then have to choose between the real
>module or
>> the translation module.
>
>That seems awkward, but I suppose doable.
>In the end, I think it's more efficient to implement such
>a function in an abstraction layer which is maintained
>independently from the DB-API database modules. Otherwise,
>you'd have to wait for all modules to implement the change
>and that can take a few years.
Perhaps the abstraction layer s
