From 0991bb911c4a77a85aac3ff651ef8590e09b9529 Mon Sep 17 00:00:00 2001 From: Jan Schatteman Date: Wed, 31 May 2023 17:46:21 +0200 Subject: [PATCH] HHH-16621 - Correct mistake in migration guide Signed-off-by: Jan Schatteman --- migration-guide.adoc | 3 --- 1 file changed, 3 deletions(-) diff --git a/migration-guide.adoc b/migration-guide.adoc index cc3eb576b2..9382553740 100644 --- a/migration-guide.adoc +++ b/migration-guide.adoc @@ -162,9 +162,6 @@ logical{fn-logical-1-1} one-to-one associations marked as optional. That is not from a modeling perspective as the foreign-key should be constrained as unique. Starting in 6.2, those UNIQUE constraints are now created. -If this causes problems for an application, creation of the UNIQUE constraint can be skipped -using `@jakarta.persistence.ForeignKey(NO_CONSTRAINT)`. - Often the association can also be remapped using `@ManyToOne` + `@UniqueConstraint` instead. [[oracle-number]]