On Thu, Mar 02, 2006 at 12:18:21AM +0100, Elrond wrote: > I intended to only put the locks as such in the db. > When it comes to a new lock, I'll select all relevant old > locks, that might conflict, handle the conflict check in > app logic and finally insert a new lock record. (all inside > a proper table lock/transaction). > > I just hoped for some cool way to let the db cleanup all > those records, when the session dies.
I don't know enough about your app to know if this would work, but if you only have the one app instance managing locks, and locks expire whenever that app dies... perhaps you can just have that app, on startup, unconditionally erase all locks in the db? -- Nathaniel -- Details are all that matters; God dwells there, and you never get to see Him if you don't struggle to get them right. -- Stephen Jay Gould
