Good point. Sadly, I'm not constructing the SQL, Django is. It could very well be that postgres is mangling the value string (thinking it's a column) ... that would possibly also explain why the exception message is truncated. I was looking at the django code last night and can't see anything obvious how it's mixing up the value with the column name. Also, there is no explicit exception handling in the django code that would be interfering with the error message.
It's on the INSERT side of the save() code (new record addition), I'm going to try removing my new field again and see if the problem goes away (I've tried everything else). Really odd. Thx for the assistance! Keep the ideas comin' -Z --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
