On Wed 11 Jul 2007, David Danier wrote:
> > Basically django simply exists whenever it gets data based from
> > postgresql.. anywhere. syncdb, inspecdb, /admin/ and everything else
> > that access the db simple die/exit with an "Aborted" message..
>
> As the changeset mentioned earlier was the unicode-merge:
> Is the datebase-encoding set to unicode?
> psql -l
List of databases
Name | Owner | Encoding
--------------+--------------+----------
djangotest | djangotest | UTF8
> Are all other steps towards unicode-support done?
I can't see what else I would have to do given that the only code I wrote was
(models.py):
from django.db import models
class Test(models.Model):
name = models.CharField(maxlength=200)
class Admin:
pass
I'll be buggered if I can see anywhere than would need unicodifying in
that....
My locale is en_GB.UTF-8 if that makes any difference, and I use a Turkish
keyboard which includes six "unicode" characters ("ğüşıöç" and caps "ĞÜŞIÖÇ)
so I am pretty sure my system works fine with unicode :-)
> (Can't see any reason, why this matters when the table is empty - as
> shown in your example...but just to be sure)
me neither :-(
--
Peter Nixon
http://peternixon.net/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
