Databases
StackOverflow2013
Postsdbo
POWhat for should I mark private variables as private if they already are?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat for should I mark private variables as private if they already are?
    primarykey
    data
    text
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USConstantin
    1. USabatishchev
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhat for should I mark private variables as private if they already are?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhat for should I mark private variables as private if they already are?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhat for should I mark private variables as private if they already are?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWell, you shouldn't. The syntax is implied and I see no reasons why you would write that because it's redundant. I prefer short syntax and I don't waste characters on meaningless sugar just because it's okay to do it. It's totally up to you to decide what you wanna do it makes no difference at all
      singulars
      1. POWhat for should I mark private variables as private if they already are?
      1. USJohn Leidegren
    2. COSee also: [Should you use the private access modifier if it's redundant?](http://stackoverflow.com/questions/254912/).
      singulars
      1. POWhat for should I mark private variables as private if they already are?
      1. USJeppe Stig Nielsen
 

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