Skip to content

PowerShell issue - empty string is upserted as NULL in DB #443

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom
Closed
VasuBhog opened this issue Nov 2, 2022 · 1 comment · Fixed by #531
Closed

PowerShell issue - empty string is upserted as NULL in DB #443

VasuBhog opened this issue Nov 2, 2022 · 1 comment · Fixed by #531
Assignees
@VasuBhog
Labels
powershell

Comments

@VasuBhog
Copy link
Contributor

VasuBhog commented Nov 2, 2022

Microsoft.Azure.WebJobs.Extensions.Sql.Tests.Integration.SqlOutputBindingIntegrationTests.AddProductParamsTest(id: 0, name: "", cost: 0, lang: PowerShell) [FAIL]

When executing scalar select Name from Products where ProductId=0
Expected: (System.String)
Actual: (System.DBNull)

This seems to be due PowerShell worker that treats empty string as Null.
@VasuBhog VasuBhog mentioned this issue Nov 3, 2022
Merged
@lucyzhang929 lucyzhang929 mentioned this issue Nov 16, 2022
Closed
@VasuBhog VasuBhog mentioned this issue Nov 22, 2022
Merged
@VasuBhog
Copy link
Contributor Author

Fixed by a workaround, but further tracked here: #535

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@VasuBhog VasuBhog

Labels
powershell
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

PowerShell NULL and function file updates Azure/azure-functions-sql-extension
2 participants
@lucyzhang929 @VasuBhog