Re: [castor-dev] Disable transaction

[Rainer M�ller]

We updated the update, create, remove methods in the DatabaseImpl that this methods persist the objects without using the TransactionContext class.

We have had many problem with long transactions. If you loaded an object in the first transaction you have to load it again in the second transaction before you could delete it. We have removed the transaction context. Now, if you want to delete an object you do not have to reload them first you can delete it directly, because we have molders which do not depend upon a transaction context.

However, you have to open (begin) and close (commit) a transaction if you want to load a object. I do not how to disable that. But you do not use the transaction context, so every object is in one transaction.

With this castor version we have much lesser problems with long transactions but we have more problems with the collections.

I do not know if this version is faster than the normal one, but it was the only way to get the application running.

Kind regards
Rainer

Enrique Rodr�guez schrieb:

any clue of what did you modify????

-----Mensaje original-----
De: Rainer M�ller [mailto:[EMAIL PROTECTED]]
Enviado el: martes, 26 de noviembre de 2002 17:52
Para: [EMAIL PROTECTED]
Asunto: Re: [castor-dev] Disable transaction


Enrique Rodr�guez schrieb:
 > The behaviour of my application don't need transactions. Can I disable
 > it?'?

We have disabled the transactions by editing the Castor code by our own,
because we had too much problems with the long transactions. As far as I
know there is no normal way to disable the transactions.

----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev