Bug #73650 [Opn]: why lose sql-results their type in PHP?

Edit report at https://bugs.php.net/bug.php?id=73650&edit=1 ID: 73650 Updated by: cmb@php.net Reported by: spam2 at rhsoft dot net -Summary: why lose sql-results there type in PHP? +Summary: why lose sql-results their type in PHP? Status: Open Type: Bug -Package: Scripting Engine problem +Package: *Database Functions PHP Version: 7.0.13 Block user comment: N Private report: N New Comment: I've changed the package to "Database Functions", even though not all database extensions are working this way, see <https://3v4l.org/07TWk>. And I don't think this is a bug – it's rather something that could be improved. Note that there are some issues, however. Cf. <https://3v4l.org/H1Sel>, for instance (the result could also be a string, but not an int, as the value overflows 64bit signed integers). Previous Comments: ------------------------------------------------------------------------ [2016-12-04 14:26:48] spam2 at rhsoft dot net Description: ------------ declare(strict_types=1); is nice but not helpful when you get from sql-queries *anything* as string and so need to use (int)$row['id_where_i_know_db_type'] on the database server you have int, longint, smallint, tinyint which are clearly int - but why is that information lost and anything casted to a string? ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=73650&edit=1