Agreed but within reason. Don't use CF for something the database is designed to do better.
-- Peter Tilbrook ColdFusion Applications Developer ColdGen Internet Solutions Manager, ACT and Region ColdFusion Users Group - http://www.actcfug.com 4/73 Tharwa Road Queanbeyan, NSW, 2620 AUSTRALIA Telephone: +61-2-6284-2727 Mobile: +61-0439-401-823 E-mail: [EMAIL PROTECTED] World Wide Web: http:/www.coldgen.com/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brett Payne-Rhodes Sent: Wednesday, 17 March 2004 7:57 PM To: CFAussie Mailing List Subject: [cfaussie] Re: Database programming Hi Ryan, Call me a dinosaur but I would never do this. You are locked in to your database vendor for life. Maintenance is a nightmare. How do you document such a system, knowing that documentation is never up to date? At least with code you can find out what is going on. With a system where the business logic is buried in the database you wind up delving through triggers and stored procedures and constraints with few if any obvious connections between them. Not to mention that 'database' programmers will probably cost significantly more than a CF programmer. You asked for thoughts. These are mine. Nobody has to agree with them... Brett B) Ryan Sabir wrote: > Hey all, > > Been doing some pretty intense study of MS-SQL server lately and a few > questions came up... > > Basically, a lot of software developers say to put all your business > logic into the database, and to support it by constraints at the > database level, instead of at the application (i.e. CF) level. This > means things like using triggers to update multiple rows in the > database, and having checks on the validity of foreign keys etc... > > The more I look at this, the more they seem to be saying to build your > entire application on the database server.... so my question is how > should Cold Fusion fit into this? > > With the XML capabilities of SQL Server 2000, it would be possible to > write an entire application in the database, and link stylesheets to > the XML output, completely bypassing CF. Has anyone tried anything > like this? > > I imagine this is not a viable method to build a serious application, > I guess because SQL and VB / C# are more cumbersome to work with than > CF.. but then where do you draw the line? How do you decide that a > particular piece of business logic is more suited to be run at the > database level, or at the application level? > > Any thoughts? > > > > ----------------------- > Ryan Sabir > Newgency Pty Ltd > 2a Broughton St > Paddington 2021 > Sydney, Australia > Ph (02) 9331 2133 > Fax (02) 9331 5199 > Mobile: 0411 512 454 > http://www.newgency.com/index.cfm?referer=rysig > > > --- > You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To > unsubscribe send a blank email to > [EMAIL PROTECTED] > > MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia > http://www.mxdu.com/ + 24-25 February, 2004 > -- Brett Payne-Rhodes Eaglehawk Computing t: +61 (0)8 9371-0471 f: +61 (0)8 9371-0470 m: +61 (0)414 371 047 e: [EMAIL PROTECTED] w: www.ehc.net.au --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004 --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
