Persistence Service in BER
Isaac Dealey
Persistence Service in the Bleading Edge Release (BER). That is, in
Subversion, but not yet in the stable build. I had built out most of the
persistence service some months ago but I never released it because I
was never entirely happy with it -- and of course too it was never
documented for the same reason. I think this new version is resolving
most of the issues I had with the previous version, so hopefully it will
find its way into the documentation and a stable release in the
not-too-distant future. :)
If you're wondering what the persistence service is, it's a more
traditional kind of ORM where you get to write Plain Old ColdFusion
Objects (POCO) and the persistence service handles all the details of
putting them in the database for you. So it will separate your business
logic from the database, as opposed to the ActiveRecord (AR) objects
where I generally just use the AR as my business object. The other
advantage is that the generic object has a smaller memory footprint than
the AR objects do, so they'll consume fewer resources while cached (and
the system will cache them for you). I don't usually actually cache my
AR objects, I usually use them as transients. There were a couple
exceptions in the member plugin for the onTap framework.
It seems like I've got it mostly working at this point. I still want to
add some cache enhancements for composed or aggregated properties and it
shares some install / uninstall code with the AR objects, so I need to
test those to make sure they're still working correctly after the
changes. And then I'll be adding it to the documentation and pushing a
new stable release.
I'm going to go ahead and put a zip of some of my test code up on the
google group for anyone who'd like to try out the BER. :)
--
[ ike ] founder - DataFaucet ORM
phone: 781.769.0723