Re: [elephant-devel] DB Transactions and UI

2007-06-28 Thread Ian Eslick
Perhaps a combination of variable isolation types and nested transactions would solve your problem. http://www.oracle.com/technology/documentation/berkeley-db/db/ref/ transapp/read.html http://www.oracle.com/technology/documentation/berkeley-db/db/ref/ transapp/nested.html Elephant supports

Re: [elephant-devel] DB Transactions and UI

2007-06-28 Thread Mariano Montone
Of course, ultimately, there is no magic that is going to solve all the variations of these kinds of problems. Even short lived transactions require that you think carefully about your application- level policies and potential side effects. In general I work from the user constraints and then t

Re: [elephant-devel] DB Transactions and UI

2007-06-28 Thread Mariano Montone
> There are cases in which a user wants to perform several operations in > a transactional way. Do you have examples? The only cases where my own apps needed several pages for an operation were creation operation, IIRC. On the other hand, there is at least one famous example, namely most online

Re: [elephant-devel] DB Transactions and UI

2007-06-28 Thread Mariano Montone
2007/6/28, Ian Eslick <[EMAIL PROTECTED]>: Just a few short comments: 1) I think that DBs are designed for certain kinds of short-running transactions, but over time have been co-opted into supporting longer and more complex ones. Which DBs are you talking about in particular? I'm interested

Re: [elephant-devel] DB Transactions and UI

2007-06-28 Thread Ian Eslick
What about the below situation: Assume there is list of open chairs of a cinema hall, user selects the chair that he wants to buy, if the transaction is short, (ie non-locking) and at the same time if another user buys that chair, who's the owner of the chair really? Application layer locking is

Re: [elephant-devel] DB Transactions and UI

2007-06-28 Thread Evrim Ulu
Ian Eslick wrote: > Just a few short comments: > > 1) I think that DBs are designed for certain kinds of short-running > transactions, but over time have been co-opted into supporting > longer and more complex ones. > > 2) User interaction takes place in a completely different domain > and I think

Re: [elephant-devel] DB Transactions and UI

2007-06-28 Thread Ian Eslick
Just a few short comments: 1) I think that DBs are designed for certain kinds of short-running transactions, but over time have been co-opted into supporting longer and more complex ones. 2) User interaction takes place in a completely different domain and I think that the constraints of

Re: [elephant-devel] DB Transactions and UI

2007-06-27 Thread Pierre THIERRY
Scribit Mariano Montone dies 27/06/2007 hora 13:12: > I've been developing web applications so far, so I'll be describing a > web UI. I've been making web apps too, mostly. I don't think it's web specific, but it's probably worse in web UIs, because they have a much worse latency than GUIs running