-
Notifications
You must be signed in to change notification settings - Fork 436
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
Support for #temp tables across requests with same connection #24
Comments
I'm quite surprised about this. It should just work. Some of the integration tests use temporary stored procedures, which should be connection-scoped in the same way. Thanks for the code. I'll look in to this. |
I sure appreciate your work on Tedious and this issue. I hope I'm not sending you down a rabbit trail, but it's not working on my machine. In case this matters, I wasn't able to use NPM to install it, so I downloaded the source as a .zip from github and copied it to my node_modules directory... a few days after you release v4. Thanks, -----Original Message----- I'm quite surprised about this. It should just work. Some of the integration tests use temporary stored procedures, which should be connection-scoped in the same way. Thanks for the code. I'll look in to this. Reply to this email directly or view it on GitHub: |
The problem relates to the scoping rules used for temporary tables (http://weblogs.sqlteam.com/mladenp/archive/2006/11/03/17197.aspx). Starting with tedious v0.0.4, the If I need to make the documentation for these two function clearer. I also wonder whether the function names are appropriate. |
Great that works in my 'real' code, as well. Thanks for your help with this.
|
Documentation updated. |
I can only use temporary tables inside the same request that creates the table. This works:
But this fails with
Invalid object name '#Tags'.
:Full sample code:
The text was updated successfully, but these errors were encountered: