Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'd say there is almost no standard.</p> <p>I've seen two ways of indenting:</p> <pre><code>Indent 1: my_dictionary = { 'uno': 'something', 'number two': 'some other thing', } Indent 2: my_dictionary = {'uno': 'something', 'number two': 'some other thing', } </code></pre> <p>I've seen three placed to have the end bracket:</p> <pre><code>End 1: my_dictionary = {'uno': 'something', 'number two': 'some other thing', } End 2: my_dictionary = {'uno': 'something', 'number two': 'some other thing', } End 3: my_dictionary = {'uno': 'something', 'number two': 'some other thing',} </code></pre> <p>And sometimes you justify the values:</p> <pre><code>my_dictionary = {'uno': 'something', 'number two': 'some other thing', } </code></pre> <p>And sometimes even the colons:</p> <pre><code>my_dictionary = {'uno' : 'something', 'number two' : 'some other thing', } </code></pre> <p>Which looks weird.</p> <p>And sometimes you have an end comma, and sometimes not:</p> <pre><code>my_dictionary = {'uno': 'something', 'number two': 'some other thing'} </code></pre> <p>And sometimes you stick it all on one row (if it fits).</p> <pre><code>my_dictionary = {'uno': 'something', 2: 'some other thing'} </code></pre> <p>Everyone seems to have their own combination of these styles. Personally I tend towards the style you use in your example, unless there is a reason not to. Common reasons not to is when you have a dictionary as a part of a statement. Like so:</p> <pre><code>amethodthattakesadict({'hey': 'this', 'looks': 'a', 'bit': 'shitty', }) </code></pre> <p>I'd recommend that you adapt yourself to the style of the guy who wrote the code you are editing. If it's your code: Do as you like. :-)</p>
    singulars
    1. This table or related slice is empty.
    1. POPython bracket convention
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USLennart Regebro
    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. CO+1 for nicely describing all the possibilities.
      singulars
      1. PO
      1. UShcs42
    2. COI think the only part of those examples actually governed by PEP8 is the spacing around the colons. Zero before, one after.
      singulars
      1. PO
      1. USTriptych
 

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