Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are two general approaches-- optimistic and pessimistic locking.</p> <p>Optimistic locking is generally much easier to implement in a web-based environment because it is fundamentally stateless. It scales much better as well. The downside is that it assumes that your users generally won't be trying to edit the same set of rows at the same time. For most applications, that's a very reasonable assumption but you'd have to verify that your application isn't one of the outliers where users would regularly be stepping on each other's toes. In optimistic locking, you would have some sort of <code>last_modified_timestamp</code> column that you would <code>SELECT</code> when a user fetched the data and then use in the <code>WHERE</code> clause when you go to update the date, i.e.</p> <pre><code>UPDATE table_name SET col1 = &lt;&lt;new value&gt;&gt;, col2 = &lt;&lt;new values&gt;&gt;, last_modified_timestamp = &lt;&lt;new timestamp&gt;&gt; WHERE primary_key = &lt;&lt;key column&gt;&gt; AND last_modified_timestamp = &lt;&lt;last modified timestamp you originally queried&gt;&gt; </code></pre> <p>If that updates 1 row, you know you were successful. Otherwise, if it updates 0 rows, you know that someone else has modified the data in the interim and you can take some action (generally showing the user the new data and asking them if they want to overwrite but you can adopt other conflict resolution approaches).</p> <p>Pessimistic locking is more challenging to implement particularly in a web-based application particularly when users can close their browser without logging out or where users may start editing some data and go to lunch before hitting <code>Submit</code>. It makes it harder to scale and generally makes the application more difficult to administer. It's really only worth considering if users will regularly try to update the same rows or if updating a row takes a large amount of time for a user so it's worth letting them know up front that someone else has locked the row.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat is the best method to make sure two people don't edit the same row on my web app?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJustin Cave
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhat is the best method to make sure two people don't edit the same row on my web app?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1: nice answer. But doesn't go into much depth - problem is that with optimisitic locking it's difficult to detect when a user has accessed a record and (therefore acquired a virtual lock) but did not subsequently update the record.
      singulars
      1. PO
      1. USsymcbean
    2. COI used a session variable to store the load form datetime and compare it to the last modified date time as per above. Very successful thanks.
      singulars
      1. PO
      1. USMr Fish
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload