Okay, I'm not fond of it. Mostly 'cause I use a lot of stored procs, triggers, functions...you know, things that databases ought to be able to do...
I try to use the database as the 'heavy lifter' in the app. That way I can take the load away from the app server layer. mySQL is an OK database for really light-weight apps. If you're working on an enterprise system, use a suitable database. The success of your application will reply on two things 1. How clean and efficient your code is. For scalability etc... 2. How robust your database is. For scalability etc... ...and I'm just a grumpy bastard when it comes down to it... <grin>Byron</grin> - You are subscribed to the CFUGToronto CFTALK ListSRV. This message has been posted by: [EMAIL PROTECTED] (Byron Bignell) To Unsubscribe, Please Visit and Login to http://www.CFUGToronto.org/ Manager: Kevin Towes ([EMAIL PROTECTED]) http://www.CFUGToronto.org/ This System has been donated by Infopreneur, Inc. (http://www.infopreneur.net)
