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

feat: New allow_na_rows_affected tweak to support NA values returned from dbGetRowsAffected() #312

Merged
merged 1 commit into from
Dec 16, 2023

Conversation

krlmlr
Copy link
Member

@krlmlr krlmlr commented Dec 16, 2023

Closes #297.

Copy link
Contributor

aviator-app bot commented Dec 16, 2023

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes.
Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This PR was merged using Aviator.


See the real-time status of this PR on the Aviator webapp.

Use the Aviator Chrome Extension to see the status of your PR within GitHub.

@krlmlr
Copy link
Member Author

krlmlr commented Dec 16, 2023

This works with RSQLite, should also work for us. Merging, happy to discuss after the fact.

@aviator-app aviator-app bot merged commit f07d948 into main Dec 16, 2023
29 checks passed
@aviator-app aviator-app bot deleted the f-297-rows-affected-na branch December 16, 2023 15:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow dbGetRowsAffected() to return a special value (e.g. -1) if this cannot be determined by the back-end
1 participant