Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74476
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.179 as permitted sender)
MIME-Version: 1.0
Sender: laruence@gmail.com
Date: Mon, 26 May 2014 14:34:04 +0800
Message-ID: <CABBJUpfoGLnep+hp=dQi6_iCTBBGN+xvLVWWeB-G5qrpZ7CF2w@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Cc: wez@php.net, Dmitry Stogov <dmitry@zend.com>
Content-Type: text/plain; charset=UTF-8
Subject: Persistent PDO supports
From: laruence@php.net (Laruence)

Hey:

      I was working on persistent PDO supports in phpng..

      and you may already know this odds behavior:

 <?php
class Foo extends PDO {
}

class Baz extends PDO {
}

$bar = new Foo("sqlite::memory:", null, null,
array(PDO::ATTR_PERSISTENT => true));
$baz = new Baz("sqlite::memory:", null, null,
array(PDO::ATTR_PERSISTENT => true));
var_dump($bar);
var_dump($baz);

?>

   it output :

object(Foo)#1 (0) {
}
object(Foo)#2 (0) {
}


     which seems very odds for me...

    anyway after the new implementation. this has been fixed , in
phpng it outputs:

object(Foo)#1 (0) {
}
object(Baz)#2 (0) {
}

     I am just not sure, is the previous behavior is on purpose?  or
any other reasons?

    if no.  then I will leave the current fix as it is...


thanks
-- 
Laruence  Xinchen Hui
http://www.laruence.com/