Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122193
Received-SPF: pass (mxe938: connection is authenticated)
MIME-Version: 1.0
Date: Fri, 19 Jan 2024 16:53:24 +0100
To: Alexander Pravdin <alex.pravdin@interi.co>
Cc: Saki Takamachi <saki@sakiot.com>, Niels Dossche
 <dossche.niels@gmail.com>, internals@lists.php.net
In-Reply-To: 
 <CAOyH9yQc=kwA2yjf48S9NP9kFj2oCBnEQzYTTZE-T-mkh7687Q@mail.gmail.com>
References: <bcca1ceb3d205fb15251d6010f91d36c@xpple.dev>
 <6246AF4D-C204-443C-9056-F662E59AA687@sakiot.com>
 <CAOyH9yQc=kwA2yjf48S9NP9kFj2oCBnEQzYTTZE-T-mkh7687Q@mail.gmail.com>
User-Agent: Roundcube Webmail/1.4.15
Message-ID: <7da714b5521026d9c2b556656bdf1d7c@xpple.dev>
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] `PDO::FETCH_CONSTRUCTOR` fetch mode proposal
From: php@xpple.dev

Hi Alexander,

> I would also suggest supporting readonly classes and creating special
> attributes to help map data fields to constructor arguments. Something 
> like
> this:
> 
> readonly class User {
>     public function  __construct(
>         #[PDOField('user_id')]
>         public string $userId,
>         #[PDOField('user_name')]
>         public string $userName,
>         #[PDOField('user_address')]
>         public ?string $userAddress = '', // Optional field with 
> default
> value
>     );
> }

When the constructor is used to create the class, readonly classes 
should be
automatically supported by this new fetch mode right? And indeed, it 
would be
useful to use named parameters if available. I overlooked this 
possibility in
my response to Saki.

Kind regards,


Frederik van der Els