siroky/Payola — comment on commit 6410ae0d2f5515b9b1309f292ead945ceeffd5b2
File: payola/common/src/main/scala/cz/payola/common/model/ParameterInstance.scala line 23
By charlieMonroe:

Depends on how you look at it - ParameterInstance is probably something the user might be changing frequently (mostly at beginning), tweaking the values to fit his needs. This would result in new object creation each time, as well as inserting it into the DB, removing the old instance, etc. I think when it's mutable, only the value in the DB would get updated. Sure, the toString method is available, but instance.intValue.toString vs. instance.stringValue - the second variant is a winner for me as it's better readable and you don't need to worry if the actual value is an int or float (if the actual value is 3.33 and you call instance.intValue.toString, you get "3", where as instance.stringValue, you get "3.33")...