-
Notifications
You must be signed in to change notification settings - Fork 177
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
Allow StringCodec
registration for CITEXT
usage
#551
Comments
Leaving https://github.com/pgjdbc/pgjdbc/blob/5c78edb1412467636f996416ad37118f651db86e/pgjdbc/src/main/java/org/postgresql/jdbc/PgPreparedStatement.java#L253-L255 here as reference. Can you upgrade to at least 0.9.2.RELEASE and bind the parameter value using It would make sense to use the same binding customization mechanism as in pgjdbc. |
I had already tried |
@mp911de |
We switched to a different group Id, |
@mp911de for |
I'm not able to reproduce the issue that you've reported. Here's my reproducer code that shows what currently works and what not:
|
We now allow registration of the StringCodec for CITEXT usage through the UNSPECIFIED OID. [resolves #551] Signed-off-by: Mark Paluch <mpaluch@vmware.com>
[#551] Signed-off-by: Mark Paluch <mpaluch@vmware.com>
[#551] Signed-off-by: Mark Paluch <mpaluch@vmware.com>
StringCodec
registration for CITEXT
usage
Bug Report
select 'text'::citext = :param
fails when:param
is set to(String) "TEST"
.This seems to be an issue with the driver explicitly setting the type of the string parameter - as noted here: https://stackoverflow.com/a/23721681/7759514
For hibernate, this can be fixed using the properties:
spring.datasource.hikari.data-source-properties.stringtype=unspecified
/spring.datasource.tomcat.connection-properties.stringtype=unspecified
However these properties seem to have no effect with r2dbc
Versions
The text was updated successfully, but these errors were encountered: