Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>Are protected members/fields really that bad?</p> </blockquote> <p><strong>No. They are way, way worse.</strong></p> <p>As soon as a member is more accessible than <code>private</code>, you are making guarantees to other classes about how that member will behave. Since a field is totally uncontrolled, putting it "out in the wild" opens your class and classes that inherit from or interact with your class to higher bug risk. There is no way to know when a field changes, no way to control who or what changes it.</p> <p>If now, or at some point in the future, any of your code ever depends on a field some certain value, you now have to add validity checks and fallback logic in case it's not the expected value - every place you use it. That's a huge amount of wasted effort when you could've just made it a damn property instead ;)</p> <p>The <strong>best</strong> way to share information with deriving classes is the <strong>read-only property</strong>:</p> <pre><code>protected object MyProperty { get; } </code></pre> <p>If you absolutely <em>have</em> to make it read/write, don't. If you really, really have to make it read-write, rethink your design. If you still need it to be read-write, apologize to your colleagues and don't do it again :)</p> <p>A lot of developers believe - and will tell you - that this is overly strict. And it's true that you can <em>get by</em> just fine without being this strict. But taking this approach will help you go from just getting by to remarkably robust software. You'll spend far less time fixing bugs.</p> <p>And regarding any concerns about performance - don't. I guarantee you will never, in your entire career, write code so fast that the bottleneck is the call stack itself.</p>
    singulars
    1. This table or related slice is empty.
    1. POAre protected members/fields really that bad?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRex M
    1. USRex M
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAre protected members/fields really that bad?
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1, more if I could. As soon as you make a member not-private, you are stuck with it, forever and ever. It's your public interface now.
      singulars
      1. PO
      1. USNikolai Fetissov
    2. COI mostly agree but I see no problem having writable protected properties. After all it is just syntactic sugar for a method with a parameter and I don't think many people would argue that protected methods must not have any parameters. (I am ignoring the slight semantic differences when choosing between a method and a property for the moment.)
      singulars
      1. PO
      1. USDaniel Brückner
    3. CO@Daniel Making a property writable adds an order of magnitude in complexity. In the real world it's definitely not realistic for *every* class to be immutable, but if most of your classes are, it's remarkably easier to write bug-free code. I had that revelation once and I hope to help others have it.
      singulars
      1. PO
      1. USRex M
 

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