Thanks Bill. Do you mean even Postgres also should have thrown errors? My worry is different here. The characters that I am getting are valid contents of a HTTP URL, and my parser is able to parse them and put in database. However, the Django interface is not able to read it. If I am required to accept that it might be some different encoding (and I will not know why type of encoded URLs I will be getting), how do I handle the same? Is there any particular settings here that can be done?
Thanks in advance. Yateen.. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
