Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You don't have to worry about it heavily depending on the situation. As is the nature of databases, you might have situations were folks reading from the database are getting 'old' information, as in they might not get information that was entered recently from when the read operation took place. If this is a big issue for your specific situation then you'll have to think about using locks, however if that isn't a big deal you should be fine.</p> <p>However, if you start getting a heavy volume of requests either to write or read, you may have to worry about locking or concurrency issues. Based on the simplicity it doesn't really sound like you have to worry much about it though.</p> <p>Regardless, make sure you handle exceptions and plan for the obvious things that could happen (connection to SQL is down, various error conditions that may be present in your code, etc.)</p> <p>I generally recommend against locking and threading unless you absolutely have a good reason to go down those paths. Threading should also be far less of an issue here due to the nature of web services, they are designed to handle concurrent usage. That is unless you have a very long running service request, then I'd move that into a thread, but, the less complexity the better.</p>
    singulars
    1. This table or related slice is empty.
    1. POMS SQL -- Okay for multiple users to connect/read/write to database from a web service (c#)?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USCapital G
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMS SQL -- Okay for multiple users to connect/read/write to database from a web service (c#)?
      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. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for responding. I'm not worried about users getting "old" data... they can refresh their interface if needed. I am just worried about errors. That said, all the relevant read/write requests are already surrounded with try/catch syntax. So, if I understand your response correctly, the only thing I might need to worry about is when there's a heavy load and someone's request might get blocked due to built-in locking etc.? If so, that's fine. The error message will be passed onto the use and he/she can just resubmit. BTW, these commands are simple INSERT/UPDATE commands anyways. Thanks.
      singulars
      1. PO
      1. USRyanM
    2. COIf you have a heavy load, your service might stop accepting requests, there are a multitude of settings you can configure for your web service to handle requests and payload sizes as well as security issues. I would recommend that when handling errors and returning the error messages, that you think about security, is it okay to give raw error messages to your users or is it smarter to send them generic messages to keep the details of your code hidden? Standard security practice is all but I wanted to mention it.
      singulars
      1. PO
      1. USCapital G
    3. COOk. Thanks for the help. Right now the load is extremely low (no more than 5 users at time), but I was trying to plan ahead. Also, thanks for the advice about security. Right now all I return is a generic error message (regardless of the actual error type), so I think I'm set there. Lastly, you mentioned settings to change for handling requests and payload sizes... can you point me to a good website with that info, or maybe some help coming up with a decent search string for Google? I'm kind of new to web services. Thanks.
      singulars
      1. PO
      1. USRyanM
 

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