-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
try catch... #36
Comments
What error do you get Manish? Does the error occur only when the catch block is executed, or does it occur regardless of whether the catch block is executed? |
it occur regardless of catch block is executed. i just un comment try...catch block from store procedure, and it give me error... |
What error do you get? Is it from the server, from tedious, or Javascript error? If the error is something like |
iisnode encountered an error when processing the request. HTTP status: 500 You are receiving this HTTP 200 response because E:...\node_modules\tedious\lib\token\token-stream-parser.js:103 Error: Unsupported ENVCHANGE type 8 BEGIN_TXN at offset 3 |
i have got 'Unsupported ENVCHANGE type' error as you mentioned. but i can't understand your given solution. |
Support for transactions has been added, which includes recognition of the ENVCHANGE tokens that relate to transactions. It is in the master branch, but has not been published to npm yet. You can clone the repo, and use npm link (or however you prefer to use a local copy of a project). Or you can wait a few days (maybe a week), and I'll publish a new version of tedious to npm. Sorry it's taken so long to get transaction support out there. |
thank you very much sir... i am waiting for 1 more week ... |
I've just published v0.0.7, which has support for transactions. |
in my store procedure in ms sql 2008, i am using try...catch... finally block.
but it gives me error.
eg.
ALTER PROCEDURE [dbo].[usp_UserFriends](@mode VARCHAR%2850%29='',
.... Some Parameter%28s%29)
AS
BEGIN
SET NOCOUNT ON
END
here i am comment out my try...catch block..
if i have to made any correction, please suggest me.
thank you very much
The text was updated successfully, but these errors were encountered: