Skip to content
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

Bug: A SQL syntax issue is being thrown if the BulkMerge is called with multiple qualifiers #850

Closed
mikependon opened this issue Jul 29, 2021 · 3 comments
Assignees
Labels
bug Something isn't working deployed Feature or bug is deployed at the current release fixed The bug, issue, incident has been fixed.

Comments

@mikependon
Copy link
Owner

mikependon commented Jul 29, 2021

Bug Description

When the BulkMerge bulk operation is being called with multiple qualifiers, a SQL exception is being thrown in relation to the syntax.

The issue is tested via dynamic invocation and not via model-based method. It might be that the issue is isolated to dynamics instead.

Exception Message:

image

Library Version:

Example: RepoDb v1.12.8 and RepoDb.SqlServer v1.1.3

@mikependon mikependon added the bug Something isn't working label Jul 29, 2021
@mikependon mikependon self-assigned this Jul 29, 2021
@mikependon
Copy link
Owner Author

Note: As per our replication steps, this happens only if all the fields on the table/model/dynamic-object were used as the qualifiers.

@mikependon
Copy link
Owner Author

How did we call it?

image

Model:
image

Schema:
image

@mikependon mikependon added the fixed The bug, issue, incident has been fixed. label Jul 30, 2021
@mikependon
Copy link
Owner Author

This will be available on the next version > RepoDb v1.12.8-beta4.

@mikependon mikependon added the deployed Feature or bug is deployed at the current release label Sep 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working deployed Feature or bug is deployed at the current release fixed The bug, issue, incident has been fixed.
Projects
None yet
Development

No branches or pull requests

1 participant