There was a diff submitted by Geert Vanderkelen awhile ago. It doesn't
apply cleanly to 'core/management.py' anymore.
Is there a reason it wasn't commited?
If I fix it to work with current release will someone commit it? I
assume svn ci is restricted.
--~--~-~--~~~---
Jacob Kaplan-Moss wrote:
> On Apr 21, 2006, at 7:10 AM, njharman wrote:
>
>>There was a diff submitted by Geert Vanderkelen awhile ago. It
>>doesn't
>>apply cleanly to 'core/management.py' anymore.
>>If I fix it to work with current release
Ticket marked wontfix. Seems rather harsh to force MySQL users into
editing output of manage.py and commands like 'install' just won't work.
Politely asking if this decision might be reconsidered if a clean
solution could be found.
If not, a warning / note in the docs about the limitations of M
It's a bit hard trying to piece together the history of this from
listarchives and tickets. It seems that putting models in a package
instead of 'models.py' should work and is believed to work.
I can verify that for MR-r2717 'models/__init__.py' does not work. In
that 'manage.py sql' produces n
Michael Radziej wrote:
> njharman wrote:
>>Ticket marked wontfix. Seems rather harsh to force MySQL users into
>>editing output of manage.py and commands like 'install' just won't work.
> Alternatively, set default table type in your database to InnoDB, and
&
DavidA wrote:
> Maybe I don't understand the implications but I have been using
> ENGINE=MyISAM on my tables so I can use MySQLs full-text indexing (not
> supported by InnoDB).
>
> Does this thread imply that I can no longer use MyISAM tables with
> MySQL? Or just that if I do, I must tweak the o
