When a user posts a requests he changes the underlying database
table. The issue is that if more users are editing the
same set of rows the last user will override the editing of the
first one. Since this is an in-house application with very few
users, we did not worry to solve this issue, which h
On Fri, Jun 5, 2009 at 2:59 PM, Tim Chase wrote:
> The common way to do this is to not bother with the "somebody else is
> editing this record" because it's nearly impossible with the stateless web
> to determine when somebody has stopped browsing a web page. Instead, each
> record simply has a "
At work we have a Web application acting as a front-end to a
database (think of a table-oriented interface, similar to
an Excel sheet). The application is accessed simultaneously by
N people (N < 10).
When a user posts a requests he changes the underlying database
table. The issue is that if more
