Re: Recover After Crash

> So they will see modifications (potentially to other tables)
> only after user will close document (transaction). This is
> not appropriate. We need to modify other tables and other
> people to see our modifications while document is open -
> all this in *one* connection.

Possibly Isolation Level 0 is O.K. for you. Typically you get a lot of ugly side effects though.

[Timestamp polling]
> I thought about this method, and it seems to work. The problem
> with it is that it obviously wastes resources (program have to
> periodically update time-stamp field).

You could also use a locking mechanism outside of the database server, if you want to spare resources:
Create a file on the server with an appropriate naming convention and open it for readwrite. The lock should be released instantly on any crash.

[Oracles proprietary Connection-ID]
> Is it the same as 'AUDSID' identifier of 'v$session' table?
> I've tried to use it, but got unsatisfactory results, see
> the other message to this thread. (In short, Oracle considers
> connection to be alive even hours after crash of workstation).

Sorry, I am not an Oracle specialist, as my signature could tell you, rather a future competitor. ;-)
I would have to dig through old documentation to find this out. IMHO a Connection-ID should be part of the API.

Maybe using Oracles lock-manager tool could get you on track, to find it.

Regards,
Carl

--
Carl Rosenberger
db4o - database for objects - http://www.db4o.com