-
Notifications
You must be signed in to change notification settings - Fork 350
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
Consider JTS Geometry types as simple types #1711
Comments
Also filed against r2dbc-postgresql |
We do not consider JTS types ( I suggest subclassing As we're not deeply involved with JTS, I suggest that you first experiment within your own domain and once you're happy with how things work, feel free to submit a pull request. |
Thanks for the pointer, I'm attempting to implement a I'm curious about the distinction between |
For anyone else trying to get this working, here's my working kotlin solution.
META-INF/spring.factories
@mp911de, I'll prepare a pull request to roll this up. As it doesn't require converters or any additional dependencies, I don't see why it couldn't be rolled straight into PostgresDialect. |
This turned out to be extremely straightforward, so I've created a pull request. Hope it saves someone else an hour or two of debugging! |
Bug Report
Creating a basic entity with a PostGIS geometry Point type does not function as expected with Spring Data R2DBC. A Point can be read from a fixture in the database using the native PostgisGeometryCodec, but cannot be inserted in a new entity.
Versions
Current Behavior
Attempting to set up a minimal mapping of a point with JTS does not work as expected with kotlin and Spring Data R2DBC. Running through a debugger, the PostgisGeometryCodec seems to be dynamically loaded during connection handshake, but this is not done in time to stop the exception being thrown on first write.
Stack trace
Steps to reproduce
Input Code
A minimal reproducible version of this bug is available here: https://github.com/pete-setchell-kubra/r2dbcrepro
Expected behavior/code
Possible Solution
This may be in issue in r2dbc-postgresql, I'll double file there and update this ticket with an issue number.
The text was updated successfully, but these errors were encountered: