Closed marzolfb closed 8 years ago
Nice work on fixing something I didn't test on my compatibility mode. Since we have no CI testing on Sybase (or SQL), did you run any bench tests to make sure your code runs against Sybase ASE?
I did perform successful bench testing against the Sybase ASE database I was working on (I should have mentioned that above). Thanks for the positive feedback.
+1 @ianic - this would be a good add to my compatibility mode and looks like it should not negatively affect the existing SQL Server functionality.
Thank you marzolfb.
You are running gofreetds tests against Sybase ASE? They are all passing or there are some Mssql specific.
Hey @ianic - thanks for merging this! I know your library wasn't really suited for Sybase but this really helps me. Also, I'm looking into setting up a CI pipeline to run tests against a SQL Server and a Sybase ASE server in the cloud. When I get it done in my fork, maybe we can discuss it and hook it up to the master - without any expense. When I do this, I will likely adapt pubs.sql to Sybase so that all the tests pass on both platforms. May take me a month to set up.
Fixes the inability to use ExecSp against a Sybase ASE database when calling a stored procedure.
This PR uses the newly-introduced Sybase compatibility mode setting on the connection string to decide whether to use a MSSQL-specific or Sybase-specific SQL command to use in getting a list of stored procedure parameters for a given stored procedure
While you can just use the Exec method to execute a stored procedure that only involves returned result sets, you are forced to use ExecSp when your stored procedure returns data in output parameters. In initial usage of ExecSp, I received this error:
Added a couple of unit tests to exercise the conditional logic as well.