On Tue, 14 Aug 2007 22:07:34 -0400 Carsten Haese <[EMAIL PROTECTED]> wrote: > weighed down by requiring a feature of such little general use, but > you're welcome to write a reusable toolkit module that lives outside of > and on top of DB-API. Of course you'll need to code some per-database > logic that defines whether the database accepts delimited identifiers > and what the delimiter is, but you only need to do this once for every > database you plan on supporting.
I'm well aware of that - and it's the tack I've taken, because - well, there's no better choice. However, this is just another toolkit on top of dbapi, so like most such, it won't work with many of them, so it'll be of interest to an even smaller set of users than something in dbapi. For the ones it does work for, it'll almost certainly have bugs that the developers of dbapi modules - presumably much more familiar with the db's in question than I am - would have caught (just one of the reasons supporting the argument for having module authors do things rather than users: the former group is much more likely to get it right). If there's not enough interest in this problem to generate interest here, there's certainly not enough for me to spend time on getting my clients to let me release it. > Keep in mind that this is just my opinion, and I don't speak for the > entire DB-SIG community. It's your right to post a proposal and ask for > a vote. I posted a proposal. The total vote was -1.... <mike -- Mike Meyer <[EMAIL PROTECTED]> http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. _______________________________________________ DB-SIG maillist - DB-SIG@python.org http://mail.python.org/mailman/listinfo/db-sig
