Hi Ryan, The system I work on was initially designed by DBAs in MS-SQL with CF just for the front end. All the important functions are handled by Stored Procedures/Functions/DTS in MS-SQL. It is a good way of going about it because a)Data manipulation is faster and more secure within the DB and b) A platform such as MS-SQL is mature so it's not as if they will change the syntax with each release a la CF. You can also be confident that MS-SQL will be around in 10 years whereas Cold Fusion you cannot be too sure on. Even if it is around it's likely that it will be different to the CF of today.
As for using XML and bypassing CF, yes it sounds good in practice but you will lose the flexibility CF gives you. The main strength of CF is the ability to develop/modify a large variety of things quickly. Things like simple updates of tables, graphs, forms, arrays, lists and a large variety of CF functions are so easy to use that it makes sense to use them in your day to day work just for the time it saves. The line between deciding to do something in CF or within the DB would have to be the complexity of what you want to do. If you need to produce an Excel file of 20,000 records with quite a bit of data manipulation then a stored proc/DTS would be the best way to go. On the other hand updating data using a form with 100 checkboxes for example is something best suited to CF. In the end it's about using each product for what it's best at. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Ryan Sabir > Sent: Wednesday, 17 March 2004 7:07 PM > To: CFAussie Mailing List > Subject: [cfaussie] Database programming > > 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 > > --- 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
