ID:               39618
 User updated by:  randy at rcs-comp dot com
 Reported By:      randy at rcs-comp dot com
 Status:           Open
-Bug Type:         Documentation problem
+Bug Type:         PDO related
 Operating System: Windows XP
 PHP Version:      5.2.0
 New Comment:

Then please address the inconstancy in the driver itself.  I will
repost for ease of reference:

Notice that the bug only appears after a prepared statement is
requested.  This means the driver itself is inconsistent in what it
returns.  If this is not a bug, then under "Actual Results" I should
have:

>php simple_pdo_test3.php
rows updated w/ exec() (some): 2 2
rows updated w/ exec() (all): 3 3 //<-- if truly not a bug, then this
should say "3 5"
statement preped and all records retrieved
rows updated w/ exec() (some): 2 2
rows updated w/ exec() (all): 3 5 
rows updated w/ exec() (some): 2 7
rows updated w/ prep & execute() (all): 3 3


Previous Comments:
------------------------------------------------------------------------

[2006-11-28 14:52:43] [EMAIL PROTECTED]

>It may be true that SQLite works this way, but if that is 
>the case, then PHP should work around this for the SQLite2 
>driver so that the PDO interface is consistant. 

.. or document it.
Please let developers to decide what to do with such kind of problems.

------------------------------------------------------------------------

[2006-11-28 14:44:50] randy at rcs-comp dot com

"Since this is the way SQLite works, we can't fix it in PHP and this
should be documented."

It may be true that SQLite works this way, but if that is the case,
then PHP should work around this for the SQLite2 driver so that the PDO
interface is consistant.  The PHP developer should not have to be
concerned with driver specific details like this.

------------------------------------------------------------------------

[2006-11-28 14:42:34] randy at rcs-comp dot com

Tony,

Sorry, I am not going to let this one drop unless someone else chimes
in.  I have been around bugs.php.net to know that you are reluctant to
fix bugs that are truly bugs.  Case in point:

http://bugs.php.net/bug.php?id=37846

This is a bug and not a documentation problem!

------------------------------------------------------------------------

[2006-11-28 14:39:00] randy at rcs-comp dot com

Another reason it is a bug is because the PDO SQLite2 driver is
inconsistent itself!

Notice that the bug only appears after a prepared statement is
requested.  If this is not a bug, then under "Actual Results" I should
have:

>php simple_pdo_test3.php
rows updated w/ exec() (some): 2 2
rows updated w/ exec() (all): 3 3 //<-- if truly not a bug, then this
should say "3 5"
statement preped and all records retrieved
rows updated w/ exec() (some): 2 2
rows updated w/ exec() (all): 3 5 
rows updated w/ exec() (some): 2 7
rows updated w/ prep & execute() (all): 3 3

------------------------------------------------------------------------

[2006-11-28 14:36:08] [EMAIL PROTECTED]

The very same issue in SQLite bug db
(http://www.sqlite.org/cvstrac/tktview?tn=383) has beem resolved by
adding it to the docs.
If you think it's wrong, then you can report it to SQLite developers
and persuade them to fix it in SQLite.

Since this is the way SQLite works, we can't fix it in PHP and this
should be documented.

>If you insist that this is a documentation problem
Yes, I do.

>will you please have another PHP developer chime in and agree with
you.
No, thank you.

------------------------------------------------------------------------

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
    http://bugs.php.net/39618

-- 
Edit this bug report at http://bugs.php.net/?id=39618&edit=1

Reply via email to