Hey,
If you get this problem with your fixtures when loading them into
MySQL InnoDB,
you can use this forked branch of Django:
https://github.com/kipanshi/django/tree/1.3.1.1
To install via pip:
pip install -e git+git://github.com/kipanshi/
django.git@1.3.1.1#egg=django-1.3.1.1
On Aug 7, 6:50 pm, Rob Hudson <[EMAIL PROTECTED]> wrote:
> > Can you get the same result with "default-storage-engine=InnoDB" in your
> > my.cnf?
>
> I believe you can but for other various reasons I'm not able to make
> this change globally.
You can let django create myisam tables, and convert
On 8/8/07, Rob Hudson <[EMAIL PROTECTED]> wrote:
>
> On Aug 6, 4:16 am, Matti Haavikko <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > Can you get the same result with "default-storage-engine=InnoDB" in your
> > my.cnf?
> >
> > - Haavikko
>
> I believe you can but for other various reasons I'm not
On Aug 6, 4:16 am, Matti Haavikko <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Can you get the same result with "default-storage-engine=InnoDB" in your
> my.cnf?
>
> - Haavikko
I believe you can but for other various reasons I'm not able to make
this change globally.
Does anyone know if adding the
how to
> force Django to create InnoDB tables with MySQL and I found that I
> need to add this to my settings.py:
>
> DATABASE_OPTIONS = {
>"init_command": "SET storage_engine=INNODB",
> }
>
> I also saw that there was a comment stating to
Hi Django Users,
I'm using MySQL with Django but I dislike MySQL's default MyISAM
tables because there is no referential integrity. So I googled how to
force Django to create InnoDB tables with MySQL and I found that I
need to add this to my settings.py:
DATABASE_OPTIONS
There's a thread from June 28 '06 on this list about changing MySQL's
storage engine from InnoDB to MyISAM for a particular table/model.
Now, an InnoDB table respects foreign keys, and a MyISAM table ignores
them. An "ALTER TABLE ... ENGINE = MyISAM" statement will fail if the
table has any
James Bennett wrote:
> On 6/28/06, Geert Vanderkelen <[EMAIL PROTECTED]> wrote:
>> I'm also not sure how you going to use the full text
>> searching unless there is a patch now too..
>
> For just querying against the DB, having fulltext indexes set up
> should be sufficient; the DB's query
On 6/28/06, Geert Vanderkelen <[EMAIL PROTECTED]> wrote:
> ALTER TABLE appname_modelname ENGINE=MyISAM;
>
> and you're done. That's something you'll have to do afterward doing a
> 'syncdb' or sqlreset indeed.
You can put that ALTER TABLE statement in the "sql" directory within
your app, named in
On 6/28/06, Geert Vanderkelen <[EMAIL PROTECTED]> wrote:
> I'm also not sure how you going to use the full text
> searching unless there is a patch now too..
For just querying against the DB, having fulltext indexes set up
should be sufficient; the DB's query optimizer will recognize that
On 6/28/06, Geert Vanderkelen <[EMAIL PROTECTED]> wrote:
> Think you made a typo there or so..
>
> MyISAM -> none transactional
> InnoDB and NDBCluster (and BDB) -> transactional
Yeah. Too much traveling, too much coding, too little sleep :(
--
"May the forces of evil become confused on the
Hi Andrew,
[EMAIL PROTECTED] wrote:
> Hi,
>
> A total newbie question here, but is there a way to specify the engine
> I would prefer when defining models for applications. Would really
> prefer MyISAM, but MySQL keeps creating InnoDB when the tables are
> automatically create
Hi James,
James Bennett wrote:
> On 6/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> A total newbie question here, but is there a way to specify the engine
>> I would prefer when defining models for applications. Would really
>> prefer MyISAM, but MySQL
On 6/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> A total newbie question here, but is there a way to specify the engine
> I would prefer when defining models for applications. Would really
> prefer MyISAM, but MySQL keeps creating InnoDB when the tables are
> aut
14 matches
Mail list logo
