> I guess my hesitation has been that I assumed[1] that my cf code would > be more portability eg developing with a mySql db and having the > production db as MS SQL.
Just in response to this - a) developing one db and then deploying on another is not a smart move. All db's have their propriety abilities, and it's in your best interest to use them. b) How often do you really change DBs on a project mid way? Mark ------------------------------------------------------------------ [EMAIL PROTECTED] ICQ: 3094740 Safe From Bees [ www.safefrombees.com ] Quoting James Cowperthwaite <[EMAIL PROTECTED]>: > Thanks for that info Taco, > > > But, as always, more reading required. > > James > > [1] Yes, I know assumption is the mother of all fuck-ups :-) > > > > On Fri, 2004-05-28 at 14:10, Taco Fleur wrote: > > 1. business logic located in the database > > 2. stored procedures execute faster as an execution plan is saved > > 3. more secure > > 4. easier to manage > > 5. return lots of result sets with only one call to the sp > > 6. easier to re-use > > 7. i could come up with more but I hope this will convince you > > > > Converting your existing queries to Stored Procedures isnt to difficult, > but whether its worth it?? I reckon from now on you should use Stored > Procedures, that will give you more benefit, unless you are also allowed to > recode the SQL statements? > > > > Taco > > > --- > 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
