Hi Taco,
This one always comes up, my opinion on this one is, it hardly ever happensWell actually it's happen quite a few times [dozen or so?] to me. In one case I had to rewrite a some of the SQL and all of the stored procs [SQL server to Oracle] and the in the other change the stored procs back to SQL [SQL server to access!]. It's usually an issue when company decide or change their SOE or change hosting environments. It hard to make even SQL 100% portable so some rework is usually required but more work is required to convert stored procs.
Stored Procedures are not hard to debug at all, most people who think so do not know about SP debugging in QA.Not hard to debug just a little harder. ie in CF code you can easily use cfdump to output queries and structures while testing and you can even set breakpoints and single step through code, look at variables etc etc. [not that I've done that in a while]
Don't need to edit it in the db, store them as .sql files and edit them with QA.As I said a little harder - you still have to drop the procedure and reload it. Query analyser does make it a little easier [unless you're using Oracle].
You forgot to mention the best advantage of stored procedures: less chance that the client (or another developer) will edit your code (as it stored in the DB) and more chance they'll need you for maintenance/changes to the site (rather than get anyone with a few months CF experience) ;-)
Justin ============================================= Justin Mclean Class Software Phone: (02) 93321230 9 Chapman St Fax: (02) 93321032 Surry Hills Mobile: 0416 119 342 NSW 2010 =============================================
--- 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
