On Fri, 2008-10-17 at 06:25 -0700, adamiis111 wrote:
> Malcom,
>
> Thanks for the well-explained response. It's a bit more complicated
> than that though as this is only an issue if the field uses a UNIQUE
> index. It is an issue up through the latest and greatest stable MySQL
> (tested on
The specific problem was already fixed at
http://code.google.com/p/django-app-plugins/issues/detail?id=11
I was speaking of the more general problem about what Pinax's stance
with regards to these type of limitations. From the limited feedback,
it sounds like our minimum standard will be UTF8
With MySQL it depends on the character set you are creating the table with.
for example with mysql 5.0.45:
mysql> create table foo ( x varchar(999), primary key (x)) character set
= 'latin1';
Query OK, 0 rows affected (0.00 sec)
mysql> create table foo2 ( x varchar(999), primary key (x))
How about we raise a validation error on UNIQUE CharField fields
greater than 255 characters for all MySQL 5.0 implementations.
I think the docs should be updated as well telling people that it's
not best practice to use CharField for fields that need more than 255
characters (or at least put a
Malcom,
Thanks for the well-explained response. It's a bit more complicated
than that though as this is only an issue if the field uses a UNIQUE
index. It is an issue up through the latest and greatest stable MySQL
(tested on 5.0.45 and no bug fixes at MySQL up through 5.0.67) and "./
The max length of a varchar field is Database dependent
MySQL it is 255
MSSQL it is 2^31-1 (2gb)
PostgreSQL it is ~ 2^20-1 (1gb)
MySQL 4.1 and greater supposedly changes any varchar or char field
with a max length or greater to 255 to a TEXT field which can hold ~
1gb
Dj Gilcrease
OpenRPG
On Thu, 2008-10-16 at 15:28 -0700, adamiis111 wrote:
> I opened up a ticket regarding a bug in the django-app-plugin with
> regards to the indexed CharField being too large
> for MySQL 5.0:
>
> http://code.google.com/p/django-app-plugins/issues/detail?id=11
>
> I think that maybe Django's
I opened up a ticket regarding a bug in the django-app-plugin with
regards to the indexed CharField being too large
for MySQL 5.0:
http://code.google.com/p/django-app-plugins/issues/detail?id=11
I think that maybe Django's handling of this should be examined more
generally for one of the
