This snippet is what you need
https://github.com/Mimino666/django-hash-field. Go ahead and give it a try,
any feedback appreciated.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from i
for my needs i will patch django/db/backends/mysql/validation.py
producing my own locally used django rpm to allow more than 255. in my
configuration this works fine. thanks all for your time and guidance!
--
You received this message because you are subscribed to the Google Groups
"Django users
On 8 déc, 19:21, germ wrote:
> > The point is that utf8 can use up to 3 bytes per character...
>
> i appreciate your reply. interesting distinction between bytes and
> chars.
Been here, done that :-/
> i think i still need some more guidance. still not sure how to
> resolve with your suggestion
On Tue, Dec 8, 2009 at 1:21 PM, germ wrote:
> > The point is that utf8 can use up to 3 bytes per character...
>
> i appreciate your reply. interesting distinction between bytes and
> chars. i think i still need some more guidance. still not sure how to
> resolve with your suggestion to consdier t
> The point is that utf8 can use up to 3 bytes per character...
i appreciate your reply. interesting distinction between bytes and
chars. i think i still need some more guidance. still not sure how to
resolve with your suggestion to consdier the character set.
i am able to create the django model
On 7 déc, 23:46, germ wrote:
> my platform: django 1.1.1, mysql 5.0.67, python 2.6.2
>
> why does syncdb complain
> CharField cannot have a "max_length" greater than 255 when using
> "unique=True"
>
> when mysql 5.0.67 does allow greater tan 255? is there
my platform: django 1.1.1, mysql 5.0.67, python 2.6.2
why does syncdb complain
CharField cannot have a "max_length" greater than 255 when using
"unique=True"
when mysql 5.0.67 does allow greater tan 255? is there a way to
override or ignore this error?
this works in mysql
7 matches
Mail list logo
