You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 25, 2023. It is now read-only.
Some database specific features are missing from this library. Rather than implementing everyone of them. It would be nice to be able to reuse an argument vectors, so that when concatenating queries, the arguments will be correctly numbered.
Yes, but sometimes one wants to use database specific function (that are not yet part of this library). Doing so with string concatenation makes it easier for onboarding rather than having to wait for every database specific feature to be available.
But you're right that in the attached example, the use case could be covered using the into_cte.
I'd like to see a PR first implementing the CTE fixes, I need to think a bit more on the other PR before accepting the solution. And I'm pretty fried after a long day already :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi !
Some database specific features are missing from this library. Rather than implementing everyone of them. It would be nice to be able to reuse an argument vectors, so that when concatenating queries, the arguments will be correctly numbered.
Something like (pseudo-code) :
The text was updated successfully, but these errors were encountered: