On 6/25/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > Interesting - I get the same behaviour. I've opened ticket #2231 for > this problem - I'll look into it.
Ok - I take that back - I don't get the same behaviour. True - the SQL doesn't get a default clause. This is by design. Default values are created python-side when the python object is created. However, I have no difficulty creating an object without specifying a responded= clause. Can you elaborate on the error message you are receiving? Side note - When validating your report, I got an SQL error too - but the problem wasn't with the default clause - it was with the SQL cursor. If the SQL cursor gets messed up because of a previous error, you might be getting misleading error reports. What do you get if you run the following in the django shell (substituting for your project names as appropriate)?: % ./manage.py shell >>> from datetime import datetime >>> from testproject.mytest.models import Response >>> r = Response(email="[EMAIL PROTECTED]", code="xxx", response_ts=datetime.now(), a1="asdf") >>> r.save() Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
