Hi Dick, On Wed, Jun 15, 2011 at 10:28 AM, Dick Wall <[email protected]> wrote:
> This does take a little getting used to, the "new" way often involves > making a database update through a DSL expression (like a SQL update > statement, which leaves the original object intact and just changes > the data in the database), and then re-querying the object to get it > in its new state, rather than just updating fields and saving the new > object. > I'm curious: do you get any concrete advantage from this, other than the fuzzy feeling that you are using immutable objects? Specifically, I'm wondering about the impact of such an approach in terms of performance and code readability. -- Cédric -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
