Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First of all, like Steven Rumbalski said, "PEP8 doesn't address this question", so it is a matter of personal preference.</p> <p>I would use a similar but not identical format as your format 3. Here is mine, and why.</p> <pre><code>my_dictionary = { # Don't think dict(...) notation has more readability "key1": 1, # Indent by one press of TAB (i.e. 4 spaces) "key2": 2, # Same indentation scale as above "key3": 3, # Keep this final comma, so that future addition won't show up as 2-lines change in code diff } # My favorite: SAME indentation AS ABOVE, to emphasize this bracket is still part of the above code block! the_next_line_of_code() # Otherwise the previous line would look like the begin of this part of code bad_example = { "foo": "bar", # Don't do this. Unnecessary indentation wastes screen space "hello": "world" # Don't do this. Omitting the comma is not good. } # You see? This line visually "joins" the next line when in a glance the_next_line_of_code() btw_this_is_a_function_with_long_name_or_with_lots_of_parameters( foo='hello world', # So I put one parameter per line bar=123, # And yeah, this extra comma here is harmless too; # I bet not many people knew/tried this. # Oh did I just show you how to write # multiple-line inline comment here? # Basically, same indentation forms a natural paragraph. ) # Indentation here. Same idea as the long dict case. the_next_line_of_code() # By the way, now you see how I prefer inline comment to document the very line. # I think this inline style is more compact. # Otherwise you will need extra blank line to split the comment and its code from others. some_normal_code() # hi this function is blah blah some_code_need_extra_explanation() some_normal_code() </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POWhat is the proper way to format a multi-line dict in Python?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRayLuo
    1. USRayLuo
    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
    1. COi like the in line comment. my first programming professor (i'd already been programming for years before) insisted on inline comments, but never effectively explained why. you've now explained a practice i've used for about 20 years.
      singulars
      1. PO
      1. USJoshua K
    2. COAha, thanks. We have similar age, experience and "mileage" in terms of programming. So if you already began that inline comment practice 20 years ago (which is impressive!), why did you still need your professor's explanation at it in presumably 10 years ago when you were in your university? Just curious. :-)
      singulars
      1. PO
      1. USRayLuo
    3. COvery good question :) ATARI BASIC and GWbasic practically forced it, being top-down flow line-based compilers. it's something i adopted as i read peter norton's BASIC (and later ASM code) in paper magazines. i learned Turbo Pascal in between, but i had already learned from the examples in the paper magazines and conformed to BASIC's limitations.
      singulars
      1. PO
      1. USJoshua K
 

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