Databases
StackOverflow2013
Postsdbo
POWrite-Only properties, what's the point?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWrite-Only properties, what's the point?
    primarykey
    data
    text
    <p>I understand why you would want to use a read-only property using the following syntax:</p> <pre><code>private int _MyInt; public int MyInt { get { return _MyInt; } } </code></pre> <p>This example probably isn't the best one because I think that read-only properties really shine in conjunction with a <code>readonly</code> variable, but that's beside the point. What I don't understand is why use a write-only property using the following syntax:</p> <pre><code>private int _MyInt; public int MyInt { set { _MyInt = value; } } </code></pre> <p>This is how read-only properties are described in various books and tutorials. If you set the variable, you would conceptually read it at <em>some</em> point, at least internally to the class, but to read it even internally within the class you would do so by accesssing <code>_MyInt</code> which I feel violates the spirit of encapsulation which properties try to enforce. Instead, why wouldn't you just use the full power of the property with different access modifies for accessing it as such:</p> <pre><code>private int _MyInt; public int MyInt { set { _MyInt = value; } private get { return _MyInt; } } </code></pre> <p>Which of course can just be written</p> <pre><code>public int MyInt { set; private get; } </code></pre> <p>You still get the encapsulation, but restrict other classes from access, so its still write-only to outside classes.</p> <p>Unless there is a case where you honestly would want to assign to a variable but never actually access it, in which case I would definitely be curious about when this need would arise.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USAnthony
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTDuplicate
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. 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. POWrite-Only properties, what's the point?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWrite-Only properties, what's the point?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWrite-Only properties, what's the point?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIf you don't want to use a particular piece of syntax, then you are welcome not to.
      singulars
      1. POWrite-Only properties, what's the point?
      1. USDavid Heffernan
    2. COAt least with WPF and the MVVM pattern, you might expose a property on the ViewModel intended for a `OneWayToSource` binding on the view. In this case, you'd only need the setter. But it doesn't disallow having a getter, too, and in fact it would be harmless (and likely useful) to include it anyway. So perhaps that still doesn't apply...
      singulars
      1. POWrite-Only properties, what's the point?
      1. USSean Hanley
    3. CO`if (False)`. What's the point?
      singulars
      1. POWrite-Only properties, what's the point?
      1. USAphex
 

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