On 11/29/05, Amit Upadhyay <[EMAIL PROTECTED]> wrote: > Each backend class grew escapeChars() method. > It raises NotImplemented if its not implemented/NotPossible if escaping can > not be done without an open connection. > Your original change tries to use escapeChars and if no exception is thrown, > but resorts to current way on exception. > On exception a warning is printed along with SQL about the problem.
That sounds good to me. I believe one of the backend db libraries (MySQLdb, maybe?) does indeed expose the parameter-quoting logic, so we could just wrap it in that case. In the other cases, we'll have to write the code. Would one of you guys volunteer to write a patch? Adrian -- Adrian Holovaty holovaty.com | djangoproject.com | chicagocrime.org
