Databases
StackOverflow2013
Postsdbo
POConstructor with all class properties or default constructor with setters?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POConstructor with all class properties or default constructor with setters?
    primarykey
    data
    text
    <p>Following are the two approaches:</p> <ul> <li>constructor with all the class properties</li> </ul> <p>Pros: I have to put an exact number of types of parameters so if I make an error the compiler warns me (by the way, is there a way to prevent the problem of having erroneously switched two Integer on the parameter list?) </p> <p>Cons: if I have lots of properties the instantiation line can become really long and it could span over two or more lines</p> <ul> <li>setters and the default empty constructor</li> </ul> <p>Pros: I can clearly see what I'm setting, so if I'm doing something wrong I can pinpoint it as soon as I'm typing it (I can't make the previuos error of switching two variables of the same type)</p> <p>Cons: the instantiation of an object with lots of properties could take several lines (don't know if this is really a con) and if I forget to set a property the compiler doesn't say anything.</p> <p>What will you do and why? Do you know of any light pattern (consider that it should be used everytime an object wth 7+ properties is instantiated) to suggest? I'm asking this because I tend to dislike large constructors where I can't figure out fast where is the variable I'm looking for, on the other hand I find the "set all properties" vulnerable to missing some of the properties.</p> <p>Feel free to argument my assumptions in pros and cons as they are only mine thoughts :)</p> <p>Update - a question I've found which is related to this: <a href="https://stackoverflow.com/questions/2848938/building-big-immutable-objects-without-using-constructors-having-long-parameter">Building big, immutable objects without using constructors having long parameter lists</a></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USAlberto Zaccagni
    plurals
    1. PL
      singulars
      1. LTLinked
    1. 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. POConstructor with all class properties or default constructor with setters?
      1. This table or related slice is empty.
      1. VTDownMod
    2. VO
      singulars
      1. POConstructor with all class properties or default constructor with setters?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POConstructor with all class properties or default constructor with setters?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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