[DB-SIG] API 3.0 limiting paramstyle to ['named', 'qmark'] is okay. ('format' is not desirable)

M.-A. Lemburg mal at egenix.com
Fri May 17 17:36:30 CEST 2013

On 17.05.2013 17:10, Christoph Zwerschke wrote:
> Am 17.05.2013 17:01, schrieb Vernon D. Cole:
>> What other options should be considered?
> Another option would be to get rid of the parameter completely, and silently accept both styles,
> whatever is used in the sql command passed to the execute method.

This would violate explicit is better than implicit, and it also
creates problems with raising proper errors, e.g. passing a
dictionary of parameters to a SQL command which uses a mix
of qmark and named style parameter markers.

We do need to keep this explicit.

Marc-Andre Lemburg

Professional Python Services directly from the Source  (#1, May 17 2013)
>>> Python Projects, Consulting and Support ...   http://www.egenix.com/
>>> mxODBC.Zope/Plone.Database.Adapter ...       http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
2013-05-07: Released mxODBC Zope DA 2.1.2 ...     http://egenix.com/go46
2013-05-06: Released mxODBC 3.2.3 ...             http://egenix.com/go45

::::: Try our mxODBC.Connect Python Database Interface for free ! ::::::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611

More information about the DB-SIG mailing list