It’s been an interesting few days (in the blogs at least) in terms of ORMs and ColdFusion. A few days ago Jason blogged about a MAX session involving ColdFusion 9 and ORMs. Then today Joe Rinehart posted a great article on the current state of ColdFusion and ORMs: Does ColdFusion have no real ORM frameworks? This was followed up by another: What makes a framework an ORM? (I’ll also point out Brian’s take as well: Joe Rinehart Stirs the Object-Relational Mapping (ORM) Frameworks Pot)
Joe’s article is pretty darn good, and drives home the real benefits an ORM framework can provide. I can personally attest to this seeing that we use Hibernate at work. Nothing is cooler than dropping all your tables as a quick way to get rid of bad data. Why can I drop all my tables? Because Hibernate will take care of recreating everything it needs.
Since the release of Transfer 1.1, I’ve been waiting to find the time to really dig into Transfer. While I agree with Joe’s arguments that we don’t have a real ORM framework in ColdFusion, at the same time (and both Joe and Brian agree here), there is some real darn good benefits to using Transfer within ColdFusion.
So with that in mind I’m launching a simple series of articles that will serve as a basic tutorial of Transfer 1.1. I hope this will be useful for others, and for me as well since I never felt like I got a good formal grounding in Transfer. Even just perusing the Transfer Overview I was surprised by some of what Transfer offered. This will hopefully be a good learning experience for everyone. If things work out right, I can wrap this before MAX and we can compare and contrast Transfer to what CF9 will offer.
The application I have in mind is a simple employee directory. Nothing earth shattering, but I’ve got the first build ready for my blog entry tomorrow and I think it works good for the first draft.