This is what we do too with a slight difference in that our triggers call stored procedures. Sometimes triggers may need to perform similar business functions (look-ups etc.) so this way we can maintain a common set of functions.
And because we call stored procedures we never have to think of the security concerns (and overhead) of checking URL vars for SQL statements. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 03, 2002 4:19 PM To: CF-Talk Subject: RE: Where is the best place to put business rules? in the great words of Adam Churvis. What would happen if someone decided to update your database using Excel ODBC connection? The stored procedure wouldn't run. But if you had your business logic in the trigger, it would fired upon an insert, update, or delete. That man knows best. Since then I put all my business logic inside of triggers. Anthony Petruzzi Webmaster 954-321-4703 http://www.sheriff.org -----Original Message----- From: Kola Oyedeji [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 03, 2002 4:17 PM To: CF-Talk Subject: RE: Where is the best place to put business rules? I've often wondered about this is there really a need for a third tier, what would you put in the third tier that you *couldn't* put in a stored proc apart from file operations? Thanks Kola > >-----Original Message----- > >From: Dave Watts [mailto:[EMAIL PROTECTED]] > >Sent: 03 April 2002 15:02 > >To: CF-Talk > >Subject: RE: Where is the best place to put business rules? > > > > > >> 1) Where is the best place to put the business rules? CF > >> Templates (using CFTransaction), or Stored Procedures (using > >> SQL Transactions). We realize that some business rules need > >> to reside on the templates, such as client side data validation. > >> But processing pages are a different story. > > > >In general, I think that stored procedures are better for any > >generic data > >manipulation tasks. Using stored procedures provides many > >advantages, such > >as more efficient processing and the ability to more easily replace or > >augment the presentation layer code. > > > >You did mention n-tier apps, and it's worth pointing out that in a > >three-tier app, the things you generally think of as "business > >rules" would > >be implemented in the middle tier, between the presentation > >layer code (CF, > >in this case) and the database. However, to the extent that your business > >rules are data manipulation issues, you're better off putting them in the > >database tier of your two-tier application. > > > >> 2) What is more likely to need clustering - the Web/CF Server, > >> or the SQL Server. > > > >The web servers are more likely to benefit from clustering, in general. > > > >Dave Watts, CTO, Fig Leaf Software > >http://www.figleaf.com/ > >voice: (202) 797-5496 > >fax: (202) 797-5444 > > > > ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. 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
