Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100868
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain roze.lv designates 213.175.74.1 as permitted sender)
To: <internals@lists.php.net>
Date: Thu, 12 Oct 2017 14:55:35 +0300
Message-ID: <000301d34351$03585950$0a090bf0$@roze.lv>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AdNDTciFb8h81mElQ2iil7bTzG2p0A==
Content-Language: lv
Subject: Mysql result data types
From: r@roze.lv ("Reinis Rozitis")

Hello,
is there a reason (technical or historical) why the data coming from =
MySQL is always strings?
I've found only one case where the data type is "honored" - =
PDO+mysqlnd+emulation off [1]

We made a fairly simple patch to 'mysqlnd' which enables (configurable =
via ini) data to be returned (trying to match) as defined in =
database/table.=20

In general something like:

switch( field->type ){
	case MYSQL_TYPE_TINY:
	case MYSQL_TYPE_SHORT:
	case MYSQL_TYPE_LONG:
	case MYSQL_TYPE_LONGLONG:
	case MYSQL_TYPE_INT24:
		convert_to_long(data);
		break;
	case MYSQL_TYPE_DECIMAL:
	case MYSQL_TYPE_DOUBLE:
	case MYSQL_TYPE_FLOAT:
	case MYSQL_TYPE_NEWDECIMAL:
		convert_to_double(data);
		break;
}

Does it make sense to create a PR and/or RFC for something like this?


[1] https://phpdelusions.net/pdo#returntypes


wbr
Reinis Rozitis