[MTOS-dev] Making MT Transaction Safe
Alvar Freude
alvar at a-blast.org
Mon Mar 10 16:11:28 PDT 2008
Hi,
-- Hirotaka Ogawa <hirotaka.ogawa at gmail.com> wrote:
> To begin making MT transaction safe and supporting InnoDB for MySQL,
> we need at least two new directives, namely EnableTransaction and
> MySQLStorageEngine.
Why not enabling transactions by default, when an appropriate RDBMS or
table type is used?
> And, MySQLStorageEngine is to specify one of MySQL Storage Engines,
> such as "InnoDB", "MyISAM", "BDB". MyISAM is selected if no
> MySQLStorageEngine specified.
hmmm, and why not selecting InnoDB as default?
The only thing I remember is, that only MyISAM can use the fulltext
indexing. But with InnoDB MySQL gets not only transactions, also foreign
key constraints etc. are enabled.
> They are more than I can handle. But, if some volunteers helped me,
> it could be realized more quickly than I now expected.
I've not too much time and much fewer knowledge about MT internals ;-) --
but can help. e.g. for the PostgreSQL part, if there is something to be
done.
Ciao
Alvar
--
** Alvar C.H. Freude, http://alvar.a-blast.org/
** http://www.assoziations-blaster.de/
** http://www.wen-waehlen.de/
** http://odem.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
Url : http://www.sixapart.com/pipermail/mtos-dev/attachments/20080311/8e5bac14/attachment.bin
More information about the MTOS-dev
mailing list