On Mar 10, 6:55 pm, Andrew Godwin wrote:
> Hi all,
>
> I'm posting this here, not as a ticket, as I'm not entirely sure it's
> Django's problem, and so would like some input*.
>
> [Base]DatabaseCreation has a method sql_indexes_for_field, which,
> handily, returns the SQL indexes for a field. Less
On 11/03/10 01:05, Russell Keith-Magee wrote:
We have an incentive to fix it too -- #12977 points out that Django's
own test suite runs foul of this problem.
Ah, that's not good.
Just documenting the problem isn't really a solution, IMHO. MySQL is
the fly in the ointment here, because it
On Thu, Mar 11, 2010 at 7:13 AM, James Bennett wrote:
> On Wed, Mar 10, 2010 at 4:55 PM, Andrew Godwin wrote:
>> The question is, is it even worth fixing? I'm tempted to conclude that
>> you're limited to shorter model/field names by your database (or use
>> db_table/db_column), but there's also
On Wed, Mar 10, 2010 at 4:55 PM, Andrew Godwin wrote:
> The question is, is it even worth fixing? I'm tempted to conclude that
> you're limited to shorter model/field names by your database (or use
> db_table/db_column), but there's also the possibility of that method using a
> much shorter way of
Hi all,
I'm posting this here, not as a ticket, as I'm not entirely sure it's
Django's problem, and so would like some input*.
[Base]DatabaseCreation has a method sql_indexes_for_field, which,
handily, returns the SQL indexes for a field. Less usefully, both
PostgreSQL and MySQL have limits
