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? Cheers for any help On Jun 18, 7:15 am, Ian <ian.g.ke...@gmail.com> wrote: > On Jun 17, 8:50 am, "c.poll...@bangor.ac.uk" <c.poll...@bangor.ac.uk> > wrote: > > > > > Hi all > > > i have an application in django that is used by our academics to apply > > for approval for projects > > > So it will be used by many different people many of whom will be cut > > and pasting scientific information from MS Word into text fields in > > django forms > > > Underneath it all is an oracle database (that i can't modify > > significantly) this has NLS_NCHAR_CHARACTERSET=AL16UTF16 and > > NLS_CHARACTERSET=WE8ISO8859P1. > > > One of the first 'real life' projects we tested it with had an alpha, > > a ™ and a couple of curly apostrophes. > > > These were rendered as ¿in django and caused an "ORA-24365: error in > > character conversion" error when trying to do a select on the oracle > > table in sql plus > > > Any help or pointers (or just somewhere to start googling) would be > > gratefully received > > What version of Django are you using, and what is the type of the > column in the database? It sounds like you're most likely using a > CLOB or a VARCHAR2, which won't be able to handle those characters > since they aren't included in ISO-8859-1. If the column is NCLOB or > NVARCHAR2, then Django should handle the encoding conversions for you. > > 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.
