Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Specifically, regarding keys: I strongly disagree with the strange idea that keys must be without meaning. In general, I consider a database a collection of facts; as soon as you start adding arbitrary numbers (like generated keys) and other irrelevant information into it, it should be a warning sign. I recommend <a href="http://www.intelligententerprise.com/030320/605celko1_1.jhtml" rel="noreferrer">this articly by Joe Celko</a> for more on keys.</p> <p>More general notes:</p> <p>Suggestions for schema designs/data models for different businesses: David C. Hay: Data Model Patterns: Conventions of Thought Rather old, but there is a reason why it's still in print <br /><a href="http://www.dorsethouse.com/books/dmp.html" rel="noreferrer">http://www.dorsethouse.com/books/dmp.html</a></p> <p>Maybe not very pattern-like, but still very good: Stephane Faroult, Peter Robson: The Art of SQL <a href="http://oreilly.com/catalog/9780596008949/" rel="noreferrer">http://oreilly.com/catalog/9780596008949/</a></p> <p>Another one which I can recommend: Vadim Tropashko: SQL Design Patterns - The Expert Guide to SQL Programming <a href="http://www.rampant-books.com/book_2006_1_sql_coding_styles.htm" rel="noreferrer">http://www.rampant-books.com/book_2006_1_sql_coding_styles.htm</a></p> <p>Systematic text-book about data modelling: Graeme Simsion &amp; Graham Witt, "Data Modeling Essentials" <a href="http://www.elsevierdirect.com/product.jsp?isbn=9780126445510" rel="noreferrer">http://www.elsevierdirect.com/product.jsp?isbn=9780126445510</a></p> <p>Maybe you are actually looking for a "style guide"?. I that case: Joe Celko: SQL Programming Style <a href="http://www.elsevierdirect.com/product.jsp?isbn=9780120887972" rel="noreferrer">http://www.elsevierdirect.com/product.jsp?isbn=9780120887972</a></p>
    singulars
    1. This table or related slice is empty.
    1. PODatabase Patterns
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTroels Arvin
    1. USTroels Arvin
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODatabase Patterns
      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. COThe risk of using 'natural' keys is that they can change; surrogate keys cannot change. Celko's article makes no value judgements on which is better. see also http://stackoverflow.com/questions/159087/composite-primary-keys-versus-unique-object-id-field#159247
      singulars
      1. PO
      1. USSteven A. Lowe
 

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