-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Reactive SQL Client Documentation Missing Information #18056
Comments
/cc @tsegismont, @vietj |
Thanks for pointing this out @ethan-gallant . I will update the doc |
tsegismont
added a commit
to tsegismont/quarkus
that referenced
this issue
Jun 22, 2021
Fixes quarkusio#18056 Reactive SQL clients use different placeholders for prepared queries. Now the database clients details section shows the differences.
tsegismont
added a commit
to tsegismont/quarkus
that referenced
this issue
Jun 22, 2021
Fixes quarkusio#18056 Reactive SQL clients use different placeholders for prepared queries. Now the database clients details section shows the differences.
gsmet
pushed a commit
to tsegismont/quarkus
that referenced
this issue
Jun 22, 2021
Fixes quarkusio#18056 Reactive SQL clients use different placeholders for prepared queries. Now the database clients details section shows the differences.
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Jun 22, 2021
Fixes quarkusio#18056 Reactive SQL clients use different placeholders for prepared queries. Now the database clients details section shows the differences. (cherry picked from commit d7ef14b)
patrox
pushed a commit
to patrox/quarkus
that referenced
this issue
Jun 23, 2021
Fixes quarkusio#18056 Reactive SQL clients use different placeholders for prepared queries. Now the database clients details section shows the differences.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
In the docs here https://quarkus.io/version/main/guides/reactive-sql-clients it says to create prepared statements with
$1 $2 $3
etc. However, this appears to be Postgres specific as the Vert.x MySQL reactive library expects arguments to be passed as Question marks?
.Expected behaviour
The docs should have a bubble stating that
?
should be used for MySQL and$1,$2,$3
etc is only applicable for Postgres SQL.Additional context
Not sure if I am missing anything here or if it's already been documented. I am not sure what the best way to iterate this information in the docs, but I would be glad to open a PR.
The text was updated successfully, but these errors were encountered: