Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104279
MIME-Version: 1.0
References: <AM0PR0702MB3684F2B7EFF1826F515BA940E2040@AM0PR0702MB3684.eurprd07.prod.outlook.com>
 <CAF+90c_vvEUYE8_bgPVL0MTJeXik6fYsiueZo644OyZubj74jQ@mail.gmail.com>
 <595b374c-bc4f-9b8a-0013-6485abbfb477@php.net> <CAF+90c8FCMtwRoJEUjBg4XPumzUGFjh0nJa82MFpFFS+WB=rxA@mail.gmail.com>
 <CAG9XoMS2q4uttDpNHPDqSLB78YK1bnS9m7qQE9oTqteGUhTAbA@mail.gmail.com>
 <CALKiJKq9geVL9tLdduPpvGVmT9D8utrQN8oLYy_jqg8hSRhRRw@mail.gmail.com>
 <41D0A782-E4E2-4B98-9C5D-174143DE9A76@gmail.com> <CAG9XoMQY7J6ykjznuAOv06rKR0mDM-JX-dKYLFOt3EnBv3+X3A@mail.gmail.com>
 <CALKiJKpWBFhcbY3CEmykWVgEu0atOfQnV4VbQHzG0MFgG5=qqw@mail.gmail.com>
 <CAG9XoMQt8xNdm3mPUMfJ00ZJHB4UN_j1-uoQTVMMBSKzWW3f_w@mail.gmail.com>
 <d5476721-ead7-11fb-9949-0a9422cd64a1@gmail.com> <CAG9XoMRwREEvwbDrayvTTQMYWKkX1khnj+_2h2qMDDC=4V7G5A@mail.gmail.com>
In-Reply-To: <CAG9XoMRwREEvwbDrayvTTQMYWKkX1khnj+_2h2qMDDC=4V7G5A@mail.gmail.com>
Date: Thu, 7 Feb 2019 10:41:59 +0000
Message-ID: <CALKiJKoh7hCiJ_LTAzpzGubab5+pavdEFgzvtqDWT2r42Zda2g@mail.gmail.com>
To: Benjamin Morel <benjamin.morel@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000b317cc05814b7e92"
Subject: Re: [PHP-DEV] Re: [RFC] [VOTE] Typed properties v2
From: rowan.collins@gmail.com (Rowan Collins)

--000000000000b317cc05814b7e92
Content-Type: text/plain; charset="UTF-8"

On Thu, 7 Feb 2019 at 09:35, Benjamin Morel <benjamin.morel@gmail.com>
wrote:

> apologies if I've missed it, but have you actually said what that use case
>> is?
>
>
> Sorry if it wasn't clear in my original post. The use case is the
> following:
>
> - a data mapper retrieves an object from the database
> - for optimization purposes, we can ask the data mapper to return a
> partial object, with only a handful of properties initialized
> - when saving the (potentially partial) entity to the database, the data
> mapper needs to read initialized properties only
>


So this entire feature request is to support something which the Doctrine
manual spends several paragraphs saying you should probably never use?

I can see that it would be elegant if this function existed, but it seems a
thin justification for adding it, when the whole problem could just be
approached a different way - e.g.add a property to the model called
$_partialFields that stores which fields were initialised.

Regards,
-- 
Rowan Collins
[IMSoP]

--000000000000b317cc05814b7e92--