[MTOS-dev] Making MT Transaction Safe

[Hirotaka Ogawa]

On Tue, Mar 11, 2008 at 8:11 AM, Alvar Freude <alvar at a-blast.org> wrote:
> 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?

Because, no commits and rollbacks are inserted into MT code.  That is,
no changes occurs if enabling this option.

At every MT::Object saves, we need to write as like:

...
if ($obj->save()) {
   MT::ObjectDriverFactory->commit;
} else {
   MT::ObjectDriverFactory->rollback;
   return $app->error(...);
}

>  > 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.

Why can it be default?

I've just made it possible to try using transaction feature for MySQL
people.  Before making it be default, we need to support doing
"transactions" and altering MyISAM tables to InnoDB, and so on.

>  > 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.

Thanks.

>
>
>  Ciao
>   Alvar
>
>
>  --
>  ** Alvar C.H. Freude, http://alvar.a-blast.org/
>  ** http://www.assoziations-blaster.de/
>  ** http://www.wen-waehlen.de/
>  ** http://odem.org/
>



-- 
Hirotaka Ogawa makes no sense.
http://as-is.net/blog/