On 3/24/08, Alex Koshelev <[EMAIL PROTECTED]> wrote:
>
> Hi, ro60
>
> There is no need in such setting. Just now you can set table engine to
> entire database or in settings.py per-connection with
>
> DATABASE_OPTIONS = {"init_command": "SET storage_engine=INNODB" }
Or to avoid this setting a
Oh! Even better. Thx for the heads up.
On Mar 25, 2:10 am, Alex Koshelev <[EMAIL PROTECTED]> wrote:
> Hi, ro60
>
> There is no need in such setting. Just now you can set table engine to
> entire database or in settings.py per-connection with
>
> DATABASE_OPTIONS = {"init_command": "SET storage_en
Hi, ro60
There is no need in such setting. Just now you can set table engine to
entire database or in settings.py per-connection with
DATABASE_OPTIONS = {"init_command": "SET storage_engine=INNODB" }
On Mar 25, 5:37 am, ro60 <[EMAIL PROTECTED]> wrote:
> Wanted to see what everyone thinks about
Wanted to see what everyone thinks about the idea of adding a patch to
allow for a setting that will automatically append a table engine type
to the create table statements generated by
django.core.management.sql.
I created a patch for my local sql.py and it seems to work well. It
consists of add
