I was approaching the conclusion that this is expected behavior. Glad to
have it confirmed with a reasonable explanation why. I guess the fix will
be to document the behavior.
Thanks,
Michael Manfre
On Fri, Jun 22, 2012 at 11:38 PM, Chris Lambacher wrote:
>
>
> On Wed, Jun 20, 2012 at 10:50 AM,
On Wed, Jun 20, 2012 at 10:50 AM, Michael Manfre wrote:
> The observed behavior is equivalent to this bit of SQL.
>
> DECLARE @retval int, @someOut int
>> exec @retval = uspReturnsAResultSetOrTwo @someOut OUTPUT
>> SELECT @retval, @someOut
>>
>
> I haven't been able to find any documentation stat
Michael:
Last time I looked at the code of django-mssql it was using a fork of
adodbapi, not the code I maintain, which is included with pywin32.
Nevertheless, I don't think there are any changes in the return parameter
handling between the two forks.
I just ran across a related page on the AS/400
I'm the maintainer of django-mssql and I've run in to an odd behavior when
trying to retrieve a stored procedure's output parameters. The parameters
(including return value) appear to only get fetched when the last recordset
for the stored procedure is loaded. This last recordset appears as if the
