Set ansi_null_dflt_on on by default #230
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I recently switched my application to use
tedious
for connecting to SQL Server 2012, which mostly went smoothly. I did however notice that some stored procedures produced errors when ran through atedious
connection, when they worked when run via ODBC or SQL Server Management Studio.By playing with the Query Options in SSMS I was able to find that I could reproduce the problem by unticking
SET ANSI_NULL_DFLT_ON
. According to MSDN the OLE DB and ODBC drivers set this flag by default. Perhapstedious
should set it too?At the same time, perhaps a way of customizing what
getInitialSql
returns would be useful, but I thought that wasn't really for me to decide. For the moment, I have duck-punched it like this: