>Well, I'd generally not design it like that. A stored procedure should do >one of two things: return the variable it says it will return or throw an >error. I'd probably have it throw a custom oracle error if the person >doesn't have permission to run it, and do a try catch in CF to trap that >specific error. > >On 11/17/05, Steve Ray <[EMAIL PROTECTED]> wrote:
I need to amend my post slightly. I referenced the wrong error code. The error I'm getting is actually '[Macromedia][Oracle JDBC Driver]Unsupported data conversion.' Thanks, Deanna. I'll pass your idea by the DBA and see what he wants to do. I'd also thought of moving the permissions logic into it's own small function, calling that and then based on the result, calling (or not calling) the main procedure. Another idea was to return the error message as a ref cursor with the same name as the original cursor (so you get back a ref cur either way, and then check to see what it contains). I think I'd prefer to do something else. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224521 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
