On Jun 18, 3:42 am, "c.poll...@bangor.ac.uk" <c.poll...@bangor.ac.uk> wrote: > Django version 1.1.2 and yes the columns in questions are nclob and > nvarchar > > The form i was using was to add the data was generated using model > formset factory > > Are there characters django just can't cope with? Do i need to clean > them out before saving the data?
No, Django uses unicode and utf8-encoded strings internally, so there should be no problems. This sounds like an Oracle-related issue to me, but have you verified that the characters are still intact just before they are saved to the database? The problem sounds similar to me to the one described here: http://groups.google.com/group/django-users/browse_thread/thread/fb812a572168bfc8?hl=en You might want to peruse that thread and see if any of the suggestions there are applicable to your case. If it is an NLS_LANG issue of some sort, then switching to a unicode build of cx_Oracle should hopefully clear it up. HTH, Ian -- 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.
