Just to add in my 2c - I think this is just one of those things where - if the wrench fits the nut use it.
I personally prefer using stored procs, but there are times where I will use CFMX instead - Generally when I want to a) Cache a query (but I mean, how easy is it to write your own caching? dead simple). b) Am using heavily dynamic SQL. (cfqueryparam gives me more security I've found, and it's just easier). Of course this is all encapsulated in layers of CFCs - so it's really a mute point. So different courses for different horses. JMHO. Mark ------------------------------------------------------------------ E: [EMAIL PROTECTED] W: www.compoundtheory.com ICQ: 3094740 Quoting Taco Fleur <[EMAIL PROTECTED]>: > > Again - not being an SP guru (but working with years of experience in writing > functions/methods) - wouldn't that relate more to the way in which the SP was > written in the first place? > [Taco Fleur] > I don't see how the way you write your SPs would solve any of this, can you > explain? > > And.... I would say to myself "The benefit of using <CFSTOREDPROC> would > still outweigh the inconvenience of specifying the NULLs.". > [Taco Fleur] > Agreed, but it makes code really messy when you can't work with named > parameters. > > > Adding to my "10 reasons" response to Anthony..... > > ....if we were to use SP's in CFMX I would be insisting that they be called > via <CFSTOREDPROC>. > > > Gary Menzel > Web Development Manager > IT Operations Brisbane -+- ABN AMRO Morgans Limited > Level 29, 123 Eagle Street BRISBANE QLD 4000 > PH: 07 333 44 828 FX: 07 3834 0828 > > > To unsubscribe from this email please forward this email to: > [EMAIL PROTECTED] > > If this communication is not intended for you and you are not an authorised > recipient of this email you are prohibited by law from dealing with or > relying on the email or any file attachments. This prohibition includes > reading, printing, copying, re-transmitting, disseminating, storing or in any > other way dealing or acting in reliance on the information. If you have > received this email in error, we request you contact ABN AMRO Morgans Limited > immediately by returning the email to [EMAIL PROTECTED] and destroy > the original. We will refund any reasonable costs associated with notifying > ABN AMRO Morgans. This email is confidential and may contain privileged > client information. ABN AMRO Morgans has taken reasonable steps to ensure the > accuracy and integrity of all its communications, including electronic > communications, but accepts no liability for materials transmitted. Materials > may also be transmitted without the knowledge of ABN AMRO Morgans. ABN AMRO > Morgans Limi! ted its directors and employees do not accept liability for the > results of any actions taken or not on the basis of the information in this > report. ABN AMRO Morgans Limited and its associates hold or may hold > securities in the companies/trusts mentioned herein. Any recommendation is > made on the basis of our research of the investment and may not suit the > specific requirements of clients. Assessments of suitability to an > individuals portfolio can only be made after an examination of the particular > clients investments, financial circumstances and requirements. > ABN AMRO Morgans Limited (ABN 49 010 669 726 AFSL 235410) A Participant of > ASX Group > --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To > unsubscribe send a blank email to [EMAIL PROTECTED] > Aussie Macromedia Developers: http://lists.daemon.com.au/ > > > Register now for the 3rd National Conference on Tourism Futures, being held > in Townsville, North Queensland 4-7 August - www.tq.com.au/tfconf > > --- > You are currently subscribed to cfaussie as: [EMAIL PROTECTED] > To unsubscribe send a blank email to [EMAIL PROTECTED] > > > Aussie Macromedia Developers: http://lists.daemon.com.au/ > --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
