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
Fix for nvarchar(max) columns on sql 2005 #340
Conversation
fixes nvarchar(max) columns on sql 2005
ping @arthurschreiber sorry ;) |
Hey there!
I'm currently on vacation, please excuse this being left aside for this long. I've taken a quick look and the patch makes sense, but I'd like to take a deeper look. I promise I'll look into this as soon as I get back home, which will be in two weeks time.
Thanks for the patch and your patience!
|
@arthurschreiber no problem, hope you have a great holiday. If theres anything you need to help resolve or diagnose this let me know. Also just realised I forgot to attach the stacktrace
|
+1 we're getting this as well. In our case, it's xml columns that appear to be returning null.
|
+1, please! Same kind of problem. The suggested patch fixes the problem. |
Hey all, Thanks for all your input. I currently don't have access to my development machine, but I'll try to get this merged and push a new release before the end of the year. Sorry for the delay and thanks for your patience! |
Fix for nvarchar(max) columns on sql 2005
Thank you! ❤️ |
Excellent! Thank you muchly! |
Thanks!! :) |
When reading nvarchar max, ensure data is not falsey fixes nvarchar(max) columns on sql 2005
see #327
not sure why this doesn't fail on sql 2008+? Somehow data is never null even if db value is null?