Yes, maybe this will be solved when Django becomes fully "unicoded".
Also, it's not a big issue, I can live with that for a while.
Maybe I can fix the data myself before saving the model.
Thanks for the help Ivan.
Best regards.
Enrico
--~--~-~--~~~---~--~~
Enrico wrote:
> Hi,
>
> It raises a "programming error":
>
> (1064, "You have an error in your SQL syntax. Check the manual that
> corresponds to your MySQL server version for the right syntax to use
> near 'WARNINGS' at line 1")
Oh... Then I'm out, don't know much about MySQL in this regard.
Hi,
It raises a "programming error":
(1064, "You have an error in your SQL syntax. Check the manual that
corresponds to your MySQL server version for the right syntax to use
near 'WARNINGS' at line 1")
Location "MySQLdb\connections.py" in defaulterrorhandler, line 33.
The backend tries to
Enrico wrote:
> Ivan, I think it's not a problem on the DB side, I'm using MySQL and
> AFAIK it just crops the string without any warning.
Then may be I am mistaken... What I'm talking about is that maxlength is
validated properly on manipulator level (method TextField.isValidLength
in
Thanks guys.
Yes, it may be an encoding issue.
The HTML form counts 10 chars, no matter what encoding, but on the
python side it can exceed the byte count.
Ivan, I think it's not a problem on the DB side, I'm using MySQL and
AFAIK it just crops the string without any warning.
Best regards.
Malcolm Tredinnick wrote:
> If I had to guess, I would say this has to do with encoding. When the
> form is submitted back to the web server, the content will be encoded
> as, say, UTF-8. The length of your input string as bytes is longer than
> 10 (since each of those characters is 2 bytes in
On Fri, 2006-09-15 at 09:29 -0700, Enrico wrote:
> Hi all,
>
> I've used the following field in a model:
>
> name = models.CharField(maxlength=10)
>
> When I type "abcdefghij", it goes ok.
>
> When I type accents, (eg.: "áéíóúáéíóú"), I get an error.
>
> The field in the admin accepts the 10
7 matches
Mail list logo
