Skip to content
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

deprecate use of Byte[] and Character[] as basic types #549

Closed
gavinking opened this issue Dec 5, 2023 · 0 comments · Fixed by #560
Closed

deprecate use of Byte[] and Character[] as basic types #549

gavinking opened this issue Dec 5, 2023 · 0 comments · Fixed by #560

Comments

@gavinking
Copy link
Contributor

gavinking commented Dec 5, 2023

Related to #394, I think we should do something like what we did with java.util.Date, warning users to stay away from the use of the basic types Byte[] and Character[]. I can't really justify why we even put these on the list in JPA 1.0, since there's no natural way to store them on most relational databases. (We intended to store them in a VARBINARY or VARCHAR, under the assumption that array contains no null elements, but then, why not use byte[] or char[] instead?)

gavinking added a commit to gavinking/jpa-api that referenced this issue Dec 5, 2023
gavinking added a commit to gavinking/jpa-api that referenced this issue Dec 5, 2023
@gavinking gavinking linked a pull request Dec 5, 2023 that will close this issue
gavinking added a commit to gavinking/jpa-api that referenced this issue Dec 5, 2023
@gavinking gavinking linked a pull request Dec 15, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
1 participant