On Wed, Feb 3, 2010 at 9:16 AM, Clinton Begin <clinton.be...@gmail.com>wrote:
> Sounds like you'd be half way to building Hibernate. :-) iBATIS doesn't > currently provide the facility to check loaded fields. > > Thanks for the information, Clinton. I see the smiley face, so I'm not offended or anything, but I am wondering what the "iBATIS" way of doing things is. I often mark records as "modified on / by". If a user opens the editor view for an object and clicks save without changing anything, I'd rather not mark the object as "modified". I also don't want to write a value the user didn't change if some other user/process changed the field while the first user was staring at the screen. I certainly don't want to bloat things. I'm coming from OpenJPA which I view as "too sophisticated" for my needs. Maybe iBATIS isn't sophisticated enough and I'm happy to add what I need (AFAIK, OpenJPA can't tell me what fields are loaded and its dirty checking isn't quite right, either). But I don't want to write anything of my own when I could be using what iBATIS provides. So checking if a field is loaded is really weak substitute for not updating a column that hasn't changed. I don't really need that feature. What I need is per-field dirty tracking. CGLIB provides a basic example of making a bound-property enhancement. I'll try to tackle that eventually unless someone here has a better solution to the problem. Thanks. -- Daryl Stultz _____________________________________ 6 Degrees Software and Consulting, Inc. http://www.6degrees.com mailto:da...@6degrees.com
