Edit report at https://bugs.php.net/bug.php?id=65690&edit=1
ID: 65690
Updated by: kalle@php.net
Reported by: slavb18 at gmail dot com
Summary: PDO_Firebird returns wrong results with numeric
15,2 and dialect 1
-Status: Assigned
+Status: Open
Type: Bug
Package: PDO Firebird
Operating System: any
PHP Version: 5.4.19
-Assigned To: mariuz
+Assigned To:
Block user comment: N
Private report: N
Previous Comments:
------------------------------------------------------------------------
[2017-01-30 08:18:19] dorin dot marcoci at gmail dot com
Slavb18,
I found this patch not so viable across Firebird dialects.
It just check for SQL_DOUBLE and sqlscale, behavior that may change and/or be different across
existing or next dialects.
Currently PDO driver connects by default using 3rd dialect and no other handling is done in terms of
specifics.
A nice solution will be to read and take into account the database dialect when connecting to a FB
database and on next operations like data fetches, parameters handling, etc...
------------------------------------------------------------------------
[2017-01-09 10:23:38] slavb18 at gmail dot com
dialect 1 is still used in legacy databases, why not fix, if patch exists for three years
------------------------------------------------------------------------
[2017-01-09 06:42:28] dorin dot marcoci at gmail dot com
Still anyone uses dialect 1? It is pending to be deprecated.
Is it worth to fix this bug? It will involve additional FB specific flag/parameter to PDO, in order
to deal right with dialects.
------------------------------------------------------------------------
[2016-03-03 13:45:31] cmb@php.net
Related To: Bug #71652
------------------------------------------------------------------------
[2013-09-17 13:28:50] slavb18 at gmail dot com
forget to attach php script:
...
$sql="select * FROM TESTPDO";
$sth = $pdo->prepare($sql);
$sth->execute();
$obj = $sth->fetch();
print_r($obj);
------------------------------------------------------------------------
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=65690
--
Edit this bug report at https://bugs.php.net/bug.php?id=65690&edit=1