On 26-Oct-07, at 10:49 AM, Robert Bunting wrote:
>> so is this a legacy database - meaning a database which had data
>> before you upgraded to unicode django? In that case, we have seen in
>> postgres that the old data is b0rked and needs to be reentered,
>> otherwise it wont work. You need to e
On Oct 24, 10:27 pm, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> so is this a legacy database - meaning a database which had data
> before you upgraded to unicode django? In that case, we have seen in
> postgres that the old data is b0rked and needs to be reentered,
> otherwise it wont work.
On 24-Oct-07, at 7:50 PM, bjornkri wrote:
> Some data IS entered into the database - when I tried just now with a
> 'content' of Greek text, I get the Incorrect string value message, but
> when I go back to the admin interface the entry is there but filled
> with question marks where the Greek t
Got it!
It was a core problem, so to speak... I tried dropping the database
and create it again, this time with the crucial (apparently) option
CHARACTER SET utf8.
So, for anyone who has the same problem:
CREATE DATABASE CHARACTER SET utf8;
It's in the manual and everything :P Did that and tr
I did that, but that made no difference. Even if the title field
doesn't have any special characters it still crashes.
Some data IS entered into the database - when I tried just now with a
'content' of Greek text, I get the Incorrect string value message, but
when I go back to the admin interface
On 24-Oct-07, at 4:42 PM, bjornkri wrote:
> def __unicode__(self):
> return self.title
def __unicode__(self):
return u"%s" % self.title<- try this
--
regards
kg
http://lawgon.livejournal.com
http://nrcfosshelpline.in/web/
--~--~-~--~~~
http://www.cnd-industry.com/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EM
Yeah, here's the model:
class Page(models.Model):
language = models.CharField(maxlength=2, choices=LANGUAGE_CHOICES)
title = models.CharField(maxlength=60)
path = models.SlugField(prepopulate_from=('language','title',))
content = models.TextField(blank=True)
class Admin():
On 24-Oct-07, at 3:37 PM, bjornkri wrote:
> 0.97-pre-SVN-6603 (just updated, had the same on -6596)
are you using the __unicode__(self):
return u"string to return"
syntax?
--
regards
kg
http://lawgon.livejournal.com
http://nrcfosshelpline.in/web/
--~
0.97-pre-SVN-6603 (just updated, had the same on -6596)
On Oct 24, 11:44 am, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> On 24-Oct-07, at 1:28 PM, bjornkri wrote:
>
> > I was sure this must be a common problem, as I've tried two different
> > installations with completely different setups, and
On 24-Oct-07, at 1:28 PM, bjornkri wrote:
> I was sure this must be a common problem, as I've tried two different
> installations with completely different setups, and the same results
> in both cases. But looking up the error message, "Incorrect string
> value", didn't give me anything
what ve
I was sure this must be a common problem, as I've tried two different
installations with completely different setups, and the same results
in both cases. But looking up the error message, "Incorrect string
value", didn't give me anything. So, sorry if this has been asked
already, blame it on a wea
12 matches
Mail list logo
