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
I noticed that query arguments are expected to be ? and via regex they will be replaced by @P{index}.
In other drivers the query is passed directly. Whether $1 or ? is the syntax to be used is up to the user.
Since regex are currently used to identify and replace the ? and not a full parser it means that string or column can't have a ?. It also means that an argument might need to be passed twice if needed twice in the query.
Avoiding the regex means a convention that the users needs be aware of which will be more complex than using just ? but does not have the above limitations.
WDYT? Is there a reason I'm missing why ? is chosen?
The text was updated successfully, but these errors were encountered:
I noticed that query arguments are expected to be
?
and via regex they will be replaced by@P{index}
.In other drivers the query is passed directly. Whether
$1
or?
is the syntax to be used is up to the user.Since regex are currently used to identify and replace the
?
and not a full parser it means that string or column can't have a?
. It also means that an argument might need to be passed twice if needed twice in the query.Avoiding the regex means a convention that the users needs be aware of which will be more complex than using just
?
but does not have the above limitations.WDYT? Is there a reason I'm missing why
?
is chosen?The text was updated successfully, but these errors were encountered: