Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I agree, code like that is going to become a maintenance headache. There's nothing wrong with the code per se, it's just that the problem is being caught too late.</p> <p>Unique constraints/indexes are a "last line of defense", at least in my world. If you want to provide a good user experience, you can't wait until the data is already being submitted to the database. You should be actively checking for duplicates at the UI level, and warning the user that s/he is about to submit a duplicate entry (and disabling the submission if duplicate keys are not allowed).</p> <p>If a duplicate key does end up being submitted, that essentially describes a bug in the application logic, so it's OK for your database to be spitting out a "database-like" error message, you don't need to try to pretty it up. The application should try to handle such errors as gracefully as possible, as with any other unexpected exception.</p> <p>If you're simply asking whether or not there's a way to modularize this kind of functionality in T-SQL... I don't think so. Not without an unholy mess of dynamic SQL, anyway.</p> <p><strong>Update</strong> - just saw a comment to the other answer, if you want to get the SQL error number back in C# then it's simple enough:</p> <pre><code>const int SqlDuplicateKeyError = 2601; try { db.Update(record); } catch (SqlException ex) { switch (ex.Number) { case SqlDuplicateKeyError: // Custom error handling here default: throw; } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POT-SQL Reporting Duplicate Key Exception to user in simple manner
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAaronaught
    1. USAaronaught
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POT-SQL Reporting Duplicate Key Exception to user in simple manner
      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. VTAcceptedByOriginator
    1. CO@Aaronaught: Checking the values against the db prior to submission looks like a good strategy. Perhaps I will add an AJAX call when the values in either textbox changes. That will also allow me to use a more generic strategy for displaying and collecting exception info. Thank you for feedback. I will post back with any progress I make. It may not be for several days though.
      singulars
      1. PO
      1. USMikeSullivan
    2. COIn a multi-user environment, you cannot rely on duplicate checks on the UI level. The UI tweaks should be there, but so should the handling of the duplicate key error. Now, since index tweaking is a common task for a DBA, letting the client parse the error message is a bad idea. Generally, it's a very bad idea to show SQL errors to the user. I definitely think MikeSullivan's solution is viable.
      singulars
      1. PO
      1. USl33t
    3. CO@l33t: This isn't parsing the error *message*, it's looking at the error *code*. That's what error codes are *for*. And as for it being a bad idea to show SQL errors to the user, it's a bad idea to show *any* specific errors to the user. Most modern applications either use fire-and-forget operations with eventual consistency, so that errors are a developer rather than user problem, and when they do need to show a genuine internal error, they do so with a generic "something went wrong" error screen and some troubleshooting steps, like "refresh the page and retry your last action".
      singulars
      1. PO
      1. USAaronaught
 

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