> I agree with Dave - putting all of your business logic > inside triggers can be a dangerous game. The best way > is to develop objects that implement your business logic > for you and these objects are then used by applications.
I don't think that's exactly what I said, or meant. I think that you could certainly use triggers for data manipulation logic, but that in a properly configured database that isn't subject to ad-hoc queries, you don't have to - you could safely use stored procedures instead. As far as developing a middle tier for business logic goes, I understand the appeal of doing that, but for most CF applications, it may be overkill, although that may change in the next version of CF, which may be a bit more friendly to that approach. In any case, I'd still want to keep core data manipulation logic as close to the data as possible, typically in stored procedures. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
