Cold fusion 11 support required for Oracle migration

[Anitha37970146wnb1]

Using cold fusion 11 we unable to viee the data from front end through stored procedure. Pls help how to modify cf script accordingly 

[MrLeG8]

Hi Anitha,

Do you have any detailed errors or issues you can share?

Do you have code now that isn't working?  Maybe we can help you modify it?

Dan

[Anitha37970146wnb1]

It's related to refcursor, using refcursor in Oracle and could not fetch the out out in front end 

[MrLeG8]

Hi Anitha,

If you truly need online help here, you'll have to be a bit more detailed than what it's "related to".

An exact error message/code and if possible snippets of the offending code shared is the only way you'll get true online help.

If, instead, you're looking for someone to hire for help, mention that and we can offer more contact information.

Hope this makes sense!

Dan

[Charlie Arehart]

Anitha, in addition to what Dan (MrLeG8) has reasonably asked, I have a few more thoughts:

• What changed, between things working and not working?
  • You refer in the title to Oracle "migration". Is it that you switched from running some old version of Oracle DB to a newer one? Note that old versions of CF don't support new versions of databases (more on CF11 being old, in a moment).
  • Or did someone apply some update to CF11 (last updated in 2019)? I ask because update 3 of CF11 had introduced an important change regarding CF calling stored procedures in Oracle and other databases, as discussed in various places, such as here.
• You're really taking grave risks in remaining on CF11, from 2014, which was last updated in 2019.
  • There have been many security fixes to CF since then that you are never going to get (including ones offered just last week in updates for CF2023 and CF2021).
  • It's a false economy to say that it's "too expensive" either to buy the current CF version ($2499 for CF Standard, for instance) or take the effort to migrate (I've helped people make that migration from CF11 to CF2023 that took just either just minutes or only hours of my time to assist them with correcting any incompatibilities. Don't presume your code "won't work" or will require "massive changes". There's no easy way to know how easily such a migration will go. The real "cost" is in testing your app under the new version--which can be done for free with the CF Developer edition.
  • Someone who firmly "will not pay for CF" can also consider Lucee, the open-source alternative CFML engine. Again, some find their migrations go very smoothly, though not always. See the last point.

I get it that some people feel their "hands are tied" in such decisions. I just wanted to put this out there, while we await your reply on other thoughts offered here.