|
|
|
|
|
by Jonathanfishner
671 days ago
|
|
Thank you for catching that issue with the STRING_AGG limit! I just pushed a fix that now supports nvarchar(max) to avoid truncation. This should resolve the issue with large outputs in MSSQL. If you still encounter any problems, please let me know. I'd love for you to give it another try and see if everything works as expected now. Your feedback is invaluable! |
|
Not sure what kills it, but without "columns" in "full_json_result" it runs through.