update the migration guide

This commit is contained in:
Steve Ebersole 2023-03-30 23:18:00 -05:00
parent 318e79ef00
commit ea83a799b2
1 changed files with 2 additions and 2 deletions

View File

@ -135,6 +135,8 @@ See link:{javadocsBase}/org/hibernate/cfg/AvailableSettings.html#WRAPPER_ARRAY_H
The main idea here is for applications using these types in the domain model to make a conscious decision about how these The main idea here is for applications using these types in the domain model to make a conscious decision about how these
values are stored. values are stored.
NOTE: Some mappings are considered implicit opt-in to the legacy behavior; e.g. using `@Lob` or `@Nationalized`
For those using such mappings, there are a few options - For those using such mappings, there are a few options -
1. Migrate the domain model to use `byte[]` and `char[]` instead. 1. Migrate the domain model to use `byte[]` and `char[]` instead.
@ -147,8 +149,6 @@ For those using such mappings, there are a few options -
d. For every result, load the Hibernate entity by primary key and set the field value to transformed result `Byte[]` or `Character[]` d. For every result, load the Hibernate entity by primary key and set the field value to transformed result `Byte[]` or `Character[]`
e. Finally, drop the old column `alter table tbl drop column array_col_old` e. Finally, drop the old column `alter table tbl drop column array_col_old`
NOTE: Some mappings are considered implicit opt-in to the legacy behavior; e.g. using `@Lob` or `@Nationalized`
[[ddl-check]] [[ddl-check]]
=== Check constraints for boolean and enum mappings === Check constraints for boolean and enum mappings
Check constraints now correctly generated for boolean and enum mappings Check constraints now correctly generated for boolean and enum mappings