Thanks Neil and Mark, I remember the whole 'active' records and really liked that concept, but to be honest I've gotten myself tied quite nicely into using stored procs recently and don't really want to move back, I'm quite happy.
I've got a small CFC setup here that generates all my beans, DAO and Gateway for my simple objects so that will probably do the job and a ORM might not be necessary, I can probably survive without all that advance stuff for the moment. One thing I would like to quickly ask, whilst on the subject of data access, how do you guys deal with encryption in an OO environment? Do you just dump the key into your app scope? Or do you create an encryption class that stores it as a property, along with the other settings and place that as a singleton into your app scope? And how do you utilize that in your DAO? Inject it as a constructor? Thanks again for your input chaps, Rob -----Original Message----- From: Robertson-Ravo, Neil (RX) [mailto:[EMAIL PROTECTED] Sent: 04 June 2007 09:25 To: CF-Talk Subject: RE: Choosing an ORM Morning, >From what I can see, it had a divorce in that it is not longer intrinsically tied into MG. With MG:U you have ORM Adaptors which means you can choose either Reactor or Transfer (or any other should they come about or exist). Stored Procs aren't going to really fit the ORM bill it really has to be direct object to table access from what I can see. What I have found with Reactor is that since it is an ActiveRecord process it has to be a 1:1 object mapping to a real physical table. It is less flexible that Transfer. With Transfer you have a little bit more flexibility with decorators but it still lacks in some areas (and excels in others) - composite keys is one area but I know Mark is working on a fix for this so it can support them. HTH N -----Original Message----- From: Robert Rawlins - Think Blue [mailto:[EMAIL PROTECTED] Sent: 04 June 2007 09:06 To: CF-Talk Subject: Choosing an ORM Hello Guys, I've just started work on a large scale rebuild of my core business application, and to aid me the gruelling task I'm toying with implementing MG, ColdSpring and one of the ORM's. I've done some small work with these in the past but used Reactor. Now, I'm sure I've read somewhere that Reactor and MG got a divorce, and that MG would most likely end up sleeping with Transfer, is this the case? Another thing to take into consideration is that I had planned to take all my queries and move them into stored procs on my SQL Server as some of them were getting pretty fat and needed a helping hand to keep performance where I want it, will I still be able to do this when working with an ORM? What are your thoughts on this stuff? What's hot? And what's not? Look forward to hearing from you guys, Rob ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJQ Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:279974 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
