Req #78855 [Com]: Native PHP types in database fetches

Edit report at https://bugs.php.net/bug.php?id=78855&edit=1 ID: 78855 Comment by: fariba dot shami326 at gmail dot com Reported by: olegxx at gmail dot com Summary: Native PHP types in database fetches Status: Open Type: Feature/Change Request Package: PostgreSQL related Operating System: Linux PHP Version: 7.2.25 Block user comment: N Private report: N New Comment: Thanks for the update and quick reply. I'll be sure to keep an eye on this thread. (https://www.mymilestonecard.bid/)github.com Previous Comments: ------------------------------------------------------------------------ [2021-04-20 11:03:09] cmb@php.net Related To: Bug #67995 ------------------------------------------------------------------------ [2020-02-13 17:10:06] cmb@php.net Related To: Bug #47051 ------------------------------------------------------------------------ [2019-11-22 13:07:32] imbolk at gmail dot com > and how is that relevant when it's about a global connection option versus add params to > each and every single command which needs massive rewrite in existing userland code to use it? Because the global option will also affect this function too. It is absolutely unclear how it should work in this case. ------------------------------------------------------------------------ [2019-11-22 12:51:59] fgfgfgfdf at somewhere dot com > We can add extension wide (php.ini) option to change > behavior of all fetch functions you can't, no RFC introducing ini options which change language behavior that way will pass in 2019 > also we can add fourth param to pg_fetch_result to return > error in it for example or you can refrain from half thougth solutions and write a proper RFC which get discussed, no way that any change in that context will go into 7.2/7.3/7.4 anyways ------------------------------------------------------------------------ [2019-11-22 12:47:32] olegxx at gmail dot com We can add extension wide (php.ini) option to change behavior of all fetch functions, also we can add fourth param to pg_fetch_result to return error in it for example. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=78855 -- Edit this bug report at https://bugs.php.net/bug.php?id=78855&edit=1