From ce3e07a1894f548ff0c08b8c686e973a9e8451e5 Mon Sep 17 00:00:00 2001 From: LiamKearn <76269376+LiamKearn@users.noreply.github.com> Date: Tue, 18 Jan 2022 13:52:01 +1100 Subject: [PATCH] DOC DBComposite reword to make a little more sense. (#10193) * Docs: DBComposite reword to make a little more sense. * Update src/ORM/FieldType/DBComposite.php Docs: Rewording DBComposite explanation based on feedback Co-authored-by: Steve Boyd --- src/ORM/FieldType/DBComposite.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/ORM/FieldType/DBComposite.php b/src/ORM/FieldType/DBComposite.php index 3b2c62e81..05423ce08 100644 --- a/src/ORM/FieldType/DBComposite.php +++ b/src/ORM/FieldType/DBComposite.php @@ -8,7 +8,7 @@ use SilverStripe\ORM\DB; use SilverStripe\ORM\Queries\SQLSelect; /** - * Apply this interface to any {@link DBField} that doesn't have a 1-1 mapping with a database field. + * Extend this class when designing a {@link DBField} that doesn't have a 1-1 mapping with a database field. * This includes multi-value fields and transformed fields * * @todo Unittests for loading and saving composite values (see GIS module for existing similar unittests)