Re: API 3.0 limiting paramstyle to ['named', 'qmark'] is okay. ('format' is not desirable)
"Vernon D. Cole" <[email protected]>
| Newsgroups | gmane.comp.python.db |
|---|---|
| Message-ID | <CAH-ZgAfm=i4TxVOjKr6neVZGniHhPvcHrNaQz0mN=t+-9keMXg@mail.gmail.com> |
If there are only the two styles, you can tell which is expected by looking at the parameters. If you have a sequence, you use 'qmark', if a mapping, you use 'named'. Follow the example of string.format() which will accept either keywords or positional args. Attempting to determine the style by scanning the SQL is expensive and not a sure thing. On Fri, May 17, 2013 at 4:15 PM, Michael Bayer <[email protected]>wrote: > > On May 17, 2013, at 11:10 AM, Christoph Zwerschke <[email protected]> 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. > > that's how dbapi3 should work for sure. for dbapi2 compatibility, some > kind of switching would be needed. > > > > > _______________________________________________ > DB-SIG maillist - [email protected] > http://mail.python.org/mailman/listinfo/db-sig > _______________________________________________ DB-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/db-sig