Re: External dirty transaction reads
Leo Mekenkamp <[email protected]>
| Newsgroups | gmane.comp.java.ozone.user |
|---|---|
| Message-ID | <1080763853.4951.13.camel@jupiter> |
On Wed, 2004-03-31 at 18:52, Tom Hazel wrote:
> Folks,
>
> Need a little help. I know ozone recommends not using explicit
> transactions, but I have a case where I would like to use them.
>
> I have searched the mailing list, google, and the code, but was unable
> to find a way to do dirty transaction reads (i.e. a non-blocking object
> read if someone has a transaction open on this object).
That's correct. Ozone has no feature where a transaction can access an
object when another transaction has a write-lock on it.
Firebird/Interbase has such a feature IIRC; a write-locked row could be
read by another transaction, and it could 'see' the unchaged (previous)
data.
> Is there a way in ozone to do something like this? Or has someone
> written an extension to do this?
Don't know, and no. I'm afraid it would be quite difficult to do it.
> And lastly. Has anyone written something that will time out transactions
> on the server side (user configurable), and/or has anyone done something
> that will abort a transaction if a client connection is broken?
Both 'no'. But these would probably be more easy than the combi
read-write stuff. Are you interested in implementing such features?
Cheers,
Leo
--
.--. .---------------.----------------------------------------.
|o_o | | Leo Mekenkamp | Free, as in 'beer' and as in 'speech': |
|:_/ | | +31 641234919 | office software http://openoffice.org |
// \ \ | | 100% java odbms http://ozone-db.org |
(| | ) | Long Live Tux | e-mail & browser http://mozilla.org |
/'\_ _/`\ | | operating system http://linux.org |
\___)=(___/ `---------------'----------------------------------------'
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click