Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <h2>You can't go wrong with the following general rules</h2> <p><strong>Validate everywhere!</strong> Where you validate determines the quality of the user experience. The closer to the user, the less safe it is but more responsive. The farther away, the safer but tends to give worse error messages.</p> <ul> <li><p>Validate at the front-end to give the user a responsive error.</p></li> <li><p>Validate in the middle to give the user nicer error messages.</p></li> <li><p>Validate in the database (constraints and such) to keep your database sane.</p></li> </ul> <p><strong>Use parameters early, and use them often!</strong> Find those square pegs early. </p> <ul> <li><p>Coerce data into the correct types as quickly as possible. (This is a form of validation.) If something is an int, don't handle it like a string.</p></li> <li><p>Don't throw away errors when checking parameters. If your regex doesn't match, or your <code>try { parse } catch { }</code> gets triggered it's important you know why and don't continue!</p></li> <li><p>Whether you use LINQ or roll-your-own SQL: do not build SQL statements with user-supplied data. <strong>EVER.</strong> Use parameterized queries and/or stored procedure calls. If you must piece-together SQL as strings, don't do it with user data. Get the "untrustworthy" data stored and manipulate it as needed later, in a separate query.</p></li> </ul> <p><strong>Encode all data passed to the user.</strong> The bad data may not be their fault, don't trash their world.</p> <ul> <li><p>Assume that anything they pass you is full of JavaScript and HTML. Assume that "binary" data will find its way in. Someone will run your web page on something other than a "browser" eventually. Your "phone number" field will be used to store an <code>.EXE</code>.</p></li> <li><p>Return all data encoded and harmless. Don't assume that "because it's in the database" (or that it's an int, or that it's just a 1 character string) that it's harmless.</p></li> <li><p>Assume that eventually your database will fail you somehow. A developer will drop in "test" data, you'll miss an edge case above, or something may run amok and insert all-purpose crap. This crap has to be passed to the user safely.</p></li> </ul> <p>Nobody's perfect: especially you. Plan for that.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do I handle user submitted data to ensure best practice programming?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USClinton Pierce
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow do I handle user submitted data to ensure best practice programming?
      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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYour first and last lines seem mutually exclusive: "You can't go wrong..." and "Nobody's perfect..."
      singulars
      1. PO
      1. USArgalatyr
    2. CO@Argalatyr lol!
      singulars
      1. PO
      1. USeglasius
    3. COI guess you were either trying to be funny or you missed the point. Do as much of this list as possible, because some of it you will screw up. Your mistakes in one part may caught elsewhere.
      singulars
      1. PO
      1. USClinton Pierce
 

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