|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #65690 PDO_Firebird returns wrong results with numeric 15,2 and dialect 1
Submitted: 2013-09-17 13:14 UTC Modified: 2017-10-24 06:45 UTC
From: slavb18 at gmail dot com Assigned:
Status: Open Package: PDO Firebird
PHP Version: 5.4.19 OS: any
Private report: No CVE-ID: None
Have you experienced this issue?
Rate the importance of this bug to you:

 [2013-09-17 13:14 UTC] slavb18 at gmail dot com
PDO_Firebird  returns wrong results with numeric (15,2) and dialect 1
dialect 1 returns numeric (15,2) as  SQL_DOUBLE and sqlscale < 0,

I know this was reported before but this report is with patch 

Test script:
create or alter procedure testpdo
returns (
    res numeric(15,2),
    res2 numeric(5,2))

Expected result:
    [RES] => 123.45
    [0] => 123.45
    [RES2] => 123.45
    [1] => 123.45

Actual result:
    [RES] => 0.04
    [0] => 0.04
    [RES2] => 123.45
    [1] => 123.45

(or any other number istead of 0.04 as variable "n" is unitilized in case of SQL_DOUBLE)


php5-bug65690.patch (last revision 2013-09-17 13:15 UTC) by slavb18 at gmail dot com)

Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2013-09-17 13:28 UTC] slavb18 at gmail dot com
forget to attach php script:

$sql="select * FROM TESTPDO";
$sth = $pdo->prepare($sql);
$obj = $sth->fetch();
 [2014-01-01 12:29 UTC]
-Package: PDO related +Package: PDO Firebird
 [2014-04-08 11:20 UTC]
-Assigned To: +Assigned To: mariuz
 [2017-01-09 06:42 UTC] 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.
 [2017-01-09 10:23 UTC] slavb18 at gmail dot com
dialect 1 is still used in legacy databases, why not fix, if patch exists for three years
 [2017-01-30 08:18 UTC] dorin dot marcoci at gmail dot com

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-10-24 06:45 UTC]
-Status: Assigned +Status: Open -Assigned To: mariuz +Assigned To:
PHP Copyright © 2001-2018 The PHP Group
All rights reserved.
Last updated: Sun Nov 19 01:31:42 2017 UTC