Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is all very subjective as per the usual code formatting debates and I do not know of any formalized conventions.</p> <p>The method I've chosen is to use all lowercase classes and ids with underscores separating words (<code>#page_container</code> for example). I declare all my <strong>tag</strong> styles first (<code>html</code>, <code>body</code>, <code>ul</code>, etc.), then all classes and ids, sorted alphabetically. Additionally, all the styles defined in each class, id, or tag are defined alphabetically as well. Using this convention makes it easier to track down a particular style.</p> <p>For formatting, I always compress it as small as possible, but still legible. I put everything on one line with appropriate white space. If you have Visual Studio, you can specify this format and have it automatically formatted this way for you (Set Style to <strong>Compact rules</strong> under <em>Tools, Options, Text Editor, CSS, Format</em>).</p> <p>Naming conventions are extremely subjective here, but the thing to keep in mind is to name your elements as their intended purpose, not their styled meaning. For example, if you have a company slogan you want to style in a large, red font name the id <code>#slogan</code> instead of <code>#red_bold</code>.</p> <p>Here's a full example to give you an idea:</p> <pre><code>body { background-color: #fff; color: #999; font-family: verdana, arial, helvetica, sans-serif; font-size: 76%; padding: 0; margin: 0; } a { color: #2c5eb4; text-decoration: none; } a:hover { text-decoration: underline; } h1, h2, h3, h4, h5, h6 { color: #f70; font-family: helvetica, verdana, arial, serif; font-weight: bold; margin: 1.2em 0; } h1 { font-size: 2.4em; line-height: 1.2em; margin-bottom: 0em; margin-top: 0em; } h2 { font-size: 1.7em; } h3 { font-size: 1.4em; } h4 { font-size: 1.2em; font-weight: bold; } h5 { font-size: 1.0em; font-weight: bold; } h6 { font-size: 0.8em; font-weight: bold; } img { border: 0; } li, ol, ul { font-size: 1.0em; line-height: 1.8em; list-style-position: inside; margin-bottom: 0.1em; margin-left: 0; margin-top: 0.2em; } #content { clear: both; margin: 0; margin-top: -4em; } #columns { height: 36em; } #column1, #column2, #column3, #column4 { border-right: 1px solid #dbdbdb; float: left; width: 18%; margin: 0 0.5em; padding: 0 1em; height: 100%; } #column1 { width: 28%; } #column1 input { float: right; } #column1 label { color: #999; float: left; } #column2 a, #column3 a { font-weight: bold; } #column4 { border-right: 0; } #form { margin: 0 2em; } .help_button { float: right; text-align: right; width: 30px; } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POCSS Conventions / Code Layout Models
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. UScowgod
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. CONot to insult your coding style — it works for you, which is the main thing — but I’ve always hated the all-on-one-line style. I find it really unreadable. There’s a convention in programming that one line of code should do one thing, to make things readable. What’s the thinking behind the all-on-one-line style?
      singulars
      1. PO
      1. USPaul D. Waite
    2. CO@Paul D. Waite Having the styles all on one line makes for a smaller file size but still legible enough to work on when necessary. Ideally, you would have some build process that compresses it even further on production, but this method is a good equilibrium between the two methods (totally compressed versus one style property per line).
      singulars
      1. PO
      1. UScowgod
    3. COMan oh man, yes, build process. Computers are there so that humans do less work, not more. YUI Compressor makes your non-gzipped files as small as possible, and gzip compression (which your server is probably doing already) is, on its own, 3 or 4 times more effective that YUI Compressor anyway. Making your code less readable is not the right way to reduce the size of files delivered to the end user.
      singulars
      1. PO
      1. USPaul D. Waite
 

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