[cfaussie] Re: CF stored proc

[Gary Menzel]

> Oohh and cfquery allows caching of a result from a stored procedure
> where cfstoredproc does not.

I can cache anything I like if I am prepared to store it in either the Application or the Session scope.  I don't need to rely on CFQUERY to do it automatically for me.  So - if CFQUERY caches it - or I cache it - the same difference (unless CFQUERY is somehow compressing the cached information - but then there is an overhead to decompress it before I can use it).

> PS. we look at things way different, you look at it from a
> portability perspective, which in my books is the lowest priority,
> in 90% of the cases its a waste of money and resources, plus it does
> not allow you to take full advantage of all the fancy stuff....

We probably do look at things differently.  But the above is not a true statement of how I look at it.  Portability is only a small part (but in this environment a relevant part).  I look at things from a pragmatic point of view - in which case "fancy stuff" gets the lowest priority because in my experience relying too much on fancy stuff ultimately costs you time and money.

Ignore the portability issue - that was only one of my "reasons".  And it is justified in this environment because - despite Ben's comments - there is always a real possibility that we could junk our DB systems and move to a different platform (it would only take one hugely major shift in one of our third party vendors for this to happen - and that could be the case within the next 6 months).

But, having said that, I happen to agree with the Ben Forta article - in the large part.  But I don't see it as an invitation to use things just because they are there.  I look at the benefits in each case.  As I said in an earlier reply.....  we do use SP's on the database - but we dont currently call them from Cold Fusion (for all the reasons - and probably more - that I replied to Anthony with).  That could change - but if it changes it will be due to a benefits analysis.  At the moments the benefits in NOT doing it outweigh the benefits in actually doing it.

Where I disagree with Ben is that the argument is a "best case" scenario where you are building the database and are in full control of it's implementation.  In most instances (at least in the current environment we have here) we dont get to build any of the major databases - they come from third parties.  So to start standardising on a methodology that we can only actually implement in a small number of cases seems to be a waste of time and resources when we have to use different methodologies to interface to these other systems.  So we use ONE methodology and then handle exceptions on a case-by-case basis.



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 Limited 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/