I've tested the application with sqlite instead of mysql and I've no
problems.
The mysql table that syncdb generate is (the mysql dump):
DROP TABLE IF EXISTS `demo_mymodel`;
SET @saved_cs_client = @@character_set_client;
SET character_set_client = utf8;
CREATE TABLE `demo_mymodel` (
`id` int(11) NOT NULL auto_increment,
`name` varchar(50) NOT NULL,
`description` varchar(200) default NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=6 DEFAULT CHARSET=latin1;
SET character_set_client = @saved_cs_client;
On Aug 21, 9:14 am, anonymous <[EMAIL PROTECTED]> wrote:
> On Aug 20, 4:05 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
>
>
>
> > Have you defined a __unicode__ method for your model? If yes, what does it
> > look like? Also are you using a binary collation?
>
> Yes, the code:
>
> class Mymodel(models.Model):
> name = models.CharField(_('name'), max_length=50)
> description = models.CharField(_('description'),max_length=200,
> blank = True, null = True)
> def __unicode__(self):
> return self.name
> class Meta:
> verbose_name = _('mymodel')
>
> "name" attribute is the one that store strings with accents.
>
> I don't know about binary collation. I've read mysql documentation,
> but don't understand if I've to define it through django or mysql and
> how.
>
> Thanks.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
