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
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 output of manage.py
(which
Hi,
njharman wrote:
> 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
>> you're
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
> you're fine.
Didn't know such a thin
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
you're fine.
Michael
--~--~-~--~~~---
