On Mon, 2009-05-04 at 08:46 -0700, MS wrote: > Hi, > > I have a problem with django+postgresql: > I have a model with a CharField(max_length=255) field, and I'm > assigning some much longer value to this field, like: > > m = MyModel() > m.myfield = 'very long text - say 400 chars' > m.save() > > In save() I'm getting an error "ERROR: value too long for type > character varying(255)", and the SQL statement contains the 'very long > text - say 400 chars' intact. > > I thought that if django knows that a field is restricted to 255 > chars, then it will validate it and > truncate excessive chars before saving. But it doesn't.
As noted elsewhere in the thread, truncating would be almost always the wrong solution, since it quietly throws away data. As for detecting the problem in the first place, form fields will already pick up this problem if the user is providing data through a form (it will be a validation error). Right now, model field validation doesn't exist, so you, as the programmer populating the field, is expected to make sure the data fits (in the above example, you're populating the model field directly, so you need to check you're populating it with something sensible). In fact, even after model field validation exists, it will still be your responsibility to make sure the data fits: Django will raise a validation error if it doesn't, but it won't automatically fix the problem because an appropriate solution is going to be domain specific. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
