On Mon, Jun 30, 2008 at 7:19 PM, Simon Tite <[EMAIL PROTECTED]> wrote:
> > However, it could be that the problem is lurking at the beginning of > > the SQL statement, which I haven't been able to see yet.... > > ...so, how does one go about looking at the actual SQL which is passed > > to the database engine? Is this possible? I suppose it must be, if I > > spent several hours diving into the Django source, but hopefully > > somebody knows an easier way? Somebody? Anybody? > > If you can recreate the problem from a python manage.py shell session, then: from django.db import connection connection.queries[-1] will show the last query sent to the database (modulo some quoting). If you cannot recreate it from a shell session you can always turn on query logging on the mysql side (assuming this is not a production database?). Details on how to do that would depend on the platform you are running MySQL on. You haven't said much about where the data for this object is coming from (other than "a form") I think? More details might help people pinpoint what is wrong. However the error you are getting is strange. If it were strings too long for the fields because of quotes you would have gotten a truncation error, not the general "there's something wrong with your sql" syntax error. There seems to be something fundamentally broken in your setup, but I have no idea what it is at this point. Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
