longevity 0.10.0 - optimistic locking

[John Sullivan]

In case you missed it, longevity 0.10.0 was release last week. The main feature for this release is optimistic locking. I was really excited about this one, because it is a realization of the promise of an essay I wrote a long time ago called Rethinking the POJO. My users never have to see a rowVersion field anywhere, let alone right there in their domain entities.

Here is the blog post I wrote about the release: Configuration-level Optimistic Locking with Longevity

Most of my non-documentation writing on longevity has gone up over at my blog under the label "longevity". But I think I'll start writing some stuff here instead. I foresee a couple non-blog-worthy releases on the horizon.. I was ready to cut in to some query enhancements, but I came up with a couple of ideas for API simplification and I am implementing them now. I want to get the API changes out so I'll probably put out a small release for that before I get on to the queries.

[John Sullivan]

My users never have to see a rowVersion field anywhere, let alone right there in their domain entities.

Okay, they will see the rowVersion (actually _modifiedDate / modified_date) in any queries made directly to the database.