PEBKAC. The query has unescaped '%' symbols in it, which causes the
query to fail. This is not reported, and instead it dies trying to log
the query in connection.queries. I'm sorry to waste your time, should
have single-stepped it before emailing in.
I was clearly using a different query to test
Hmm, I'm not sure why issuing a query previously isn't fixing it - South
just uses the same database cursors that the rest of Django uses, it's one
of the few things we don't mess around with.
Surely Django has to have some code to deal with the case when there isn't
that attribute already? Have y
Hi all
I've just run into a slight problem with Django 1.4.1, south 0.7.6 and
py-MySQLdb 1.2.3.
In the fix for Django bug #14091, Django will now always look at
cursor._last_executed in order to get details of the last query
executed, which I guess is for managing connection.queries in debug
mode
3 matches
Mail list logo