Re^3: Recoding a multi-sql-statement storedProc transaction in a script

Patient: Doctor, it hurts when I do this.
Doctor: Don't do that.

I guess I just don't get it. You had working SQL that did what you wanted in a stored proc that you called from your program. Now you want to take it apart, and reconstitute the pieces into your program, and you're finding it painful. So... Is there any reason why you're re-writing it, other than to prove that you don't like pain?

Do not rebuke them with harsh words ... but rather lead them gently - with URLs - so that they may learn wisdom.

Comment on Re^3: Recoding a multi-sql-statement storedProc transaction in a script

Replies are listed 'Best First'.
Re^4: Recoding a multi-sql-statement storedProc transaction in a script by punkish (Priest) on Dec 15, 2004 at 02:00 UTC
So... Is there any reason why you're re-writing it Because, in the earlier version I had access to the db to add my storedproc to it. Now, in this new instance, there is a possibility that I may not be able to muck around with the db, so I just want to be prepared with a working version of my SQLs in my script.	[reply]