-
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
LocalDate, LocalDateTime are not DATE, not TIMESTAMP #1867
Comments
Sorry, I have a hard time understanding what your question is. This part:
doesn't seem to be related to the rest of the question at all, correct? Please provide a Minimimal Reproducable Example, preferable as a Github repository. Make sure to include the database, either as an in memory database or if that is not possible using Testcontainers. |
Spring Data JDBC for LocalDate, LocalDateTime data types used SqlType TIMESTAMP и UNKNOW, I expect DATE and TIMESTAMP JdbcUtil.java convertation: Based on the motives: spring-projects/spring-framework#28778 |
Still, what is the actual problem? Does data get stored wrongly? Please provide a sample. |
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed. |
Hello!
Problem is resolved |
I don't think there is anything here to do for us. |
Based on the motives: spring-projects/spring-framework#28778
I conclude that LocalDate is a DATE sqlCode and LocalDateTime is a TIMESTAMP.
but in JdbcUtil:
https://github.com/spring-projects/spring-data-relational/blob/main/spring-data-jdbc/src/main/java/org/springframework/data/jdbc/support/JdbcUtil.java
I didn't quite understand what happened to these types?
I using 3.3.3 version, and have UNKNOWN type for LocalDateTime, Timestamp for LocalDate
PROPERTY TYPE: class java.time.LocalDate -> class java.sql.Timestamp -> TIMESTAMP
PROPERTY TYPE: class java.time.LocalDateTime -> class java.time.LocalDateTime -> UNKNOWN
The text was updated successfully, but these errors were encountered: