From 55dc02c39f540aaee5c8dee0e5908b5b21e3bf56 Mon Sep 17 00:00:00 2001 From: Florian Sylvain Date: Tue, 31 Dec 2024 00:09:28 +0100 Subject: [PATCH] changed confusing negative wording (#11775) --- docs/en/reference/inheritance-mapping.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/reference/inheritance-mapping.rst b/docs/en/reference/inheritance-mapping.rst index 38696dd22a0..f06341810c0 100644 --- a/docs/en/reference/inheritance-mapping.rst +++ b/docs/en/reference/inheritance-mapping.rst @@ -16,7 +16,7 @@ is common to multiple entity classes. Mapped superclasses, just as regular, non-mapped classes, can appear in the middle of an otherwise mapped inheritance hierarchy (through Single Table Inheritance or Class Table Inheritance). They -are not query-able, and need not have an ``#[Id]`` property. +are not query-able, and do not require an ``#[Id]`` property. No database table will be created for a mapped superclass itself, only for entity classes inheriting from it. That implies that a