[opencms-dev] Re: Transactional integrity - is there any?

[Jonathan Woods]

Christoph - no, I didn't ever get an answer.
 
I've since come to suspect that's because most open source applications
which rely primarily on MySQL aren't transactional at the database level.
In turn, I imagine this is because a transactional MySQL engine came
relatively late to the party.  I agree with you, though - it ought to be a
feature of the design.  The usual justification for it not being so is that
in the web app world you're dealing largely with read-only transactions, not
with updates.
Jon

  _____  

From: opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org] On Behalf Of Christoph Schönfeld
Sent: 18 October 2006 15:36
To: The OpenCms mailing list
Subject: [opencms-dev] Re: Transactional integrity - is there any?


Hi all,

surprisingly to me, OpenCms does not seem to make use of database
transactions. Last year, Jonathan Woods asked about transactions. Jonathan,
did you get an answer to your questions? 

Today, I found out that Alcacon GmbH provides a "Transaction Manager"
component as part of its commercial "OCEE" add-on to OpenCms. 

The mailing list is also very silent on this topic. Is the demand for
transactional processing so low or did all of you just buy the OCEE?

It is a pity that such a critical feature is available only for money. I
would expect from any software, be it commercial or open source, to make use
of database transactions out of the box.

Does anybody know if the "Transaction Manager" is available separate from
the OCEE pack? I do not need the whole pack, just the transactions. 

Secondly, I would like to know what the Transaction Manager does exactly and
how it works. Where does it secure processing? Which classes are does it
replace?

Greetings from Hamburg,
    Christoph

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20061018/33cc4bfe/attachment.htm>