[CONJ-1083] Using /*client prepare*/ prefix to force client side prepared statement Created: 2023-06-07 Updated: 2023-06-08 Resolved: 2023-06-07 |
|
| Status: | Closed |
| Project: | MariaDB Connector/J |
| Component/s: | Other |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.0 |
| Type: | Task | Priority: | Major |
| Reporter: | Diego Dupin | Assignee: | Diego Dupin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
When option `useServerPrepStmts` is set, every prepared statement will use server side prepared statement. There is some specific command where user might prefer to use server side prepared statement. Goal here is that commands prefixed with
will use client side prepared statement when `useServerPrepStmts` is enable. |
| Comments |
| Comment by Vladislav Vaintroub [ 2023-06-08 ] |
|
while not very important, I think "text" is not an ideal marker for that. There is client-side or server-side prepared statements, it is what meant here. , while "text" vs "binary" is just encoding of the result set row, nothing else. So , I think /* client prepare / and / server prepare / or anything that emphasize client-side vs server-side is better than / text / or / binary / . Even / c */ is |
| Comment by Diego Dupin [ 2023-06-08 ] |
|
good remark. changed with https://github.com/mariadb-corporation/mariadb-connector-j/commit/ad61d55e9c4c7c923ada10813bc7963a66897f29 |