I can release pymssql 1.1.0 with callproc tomorrow if somebody donates the code. I'm out of resources and this is not gonna change for several months...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was thinking of having a look at it when I get a bit of free time since we make heavy use sprocs at work so having callproc would be incredibly useful. Just wanted to check that you weren't already working on it to save duplicating efforts.
Keep in mind also http://msdn.microsoft.com/en-us/library/aa937108\(SQL.80).aspx because pymssql is hoping to be more-or-less portable ;-)
Seriously if the prototypes for both platforms are the same, there's no problem. I use Windows as my primary development platform, so I can test it.
We can discuss details via email, just use akukula+pymssql gmail com
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was wondering if you have any plans to implement callproc?
I can release pymssql 1.1.0 with callproc tomorrow if somebody donates the code. I'm out of resources and this is not gonna change for several months...
I was thinking of having a look at it when I get a bit of free time since we make heavy use sprocs at work so having callproc would be incredibly useful. Just wanted to check that you weren't already working on it to save duplicating efforts.
I'm guessing that http://www.freetds.org/reference/a00276.html is the place to look for freetds regarding procedures?
No I didn't do anything yet.
Keep in mind also http://msdn.microsoft.com/en-us/library/aa937108\(SQL.80).aspx because pymssql is hoping to be more-or-less portable ;-)
Seriously if the prototypes for both platforms are the same, there's no problem. I use Windows as my primary development platform, so I can test it.
We can discuss details via email, just use akukula+pymssql gmail com