On Aug 15, Jesper Noehr <[EMAIL PROTECTED]> wrote:
> Hey guys,
Hi!
> Great to see the 3.x release coming along nicely!
Looks stable enough. (last famous words ;-)
> Why does the SQL subsystem for MySQL insist on using MyISAM?
No real reason: it's still the default (correct?) for MySQL,
and there is not an easy way to set it in SQLObject, for the user.
Anyway, it seem possible to hard-code it:
class SomeObject(SQLObject):
class sqlmeta:
createSQL = {'mysql' : 'ALTER TABLE some_object ENGINE InnoDB'}
I'm not sure if there are drawbacks: are there versions of
MySQL without InnoDB support still in use around the world?
Maybe it's possible to let the user set the preferred engine, but
it doesn't appear an easy task: the only way would be to modify/extend
the URI schema used by SQLObject, but it doesn't seem a very
smart move... :-/
Besides this, it's always possible to set it server-side, but you
need admin access to change the default-storage-engine and
the default-table-type setting. :-/
> It might be faster, but it also locks per table-level which makes
> it virtually impossible to do any effecient threading on the dataset.
Yep; a lot of time ago I tested the performances _at insert time_ and
InnoDB showed some unpleasant results, but probably it was just some
fault in my configuration/setup/version/computer/head. ;-)
> If there's no obvious reason for choosing MyISAM, can it be an
> option to select either that or InnoDB?
I'm not sure if SQLAlchemy supports this feature; anyway, I fear I'm
too lazy to consider a switch. :-)
I'll do some tests for performances and I'll look for an easy way to
let the user choose; maybe it's easier than it looks.
Thanks!
--
Davide Alberani <[EMAIL PROTECTED]> [PGP KeyID: 0x465BFD47]
http://erlug.linux.it/~da/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Imdbpy-devel mailing list
Imdbpy-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
