Re: DB_Result fetchRow() && fetchInto()
| From: | Roman Neuhauser | Date: | Thu, 12 Jun 2003 12:36:45 +0000 |
| Subject: | Re: DB_Result fetchRow() && fetchInto() | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-17357@lists.php.net to get a copy of this message | ||
# neuhauser@bellavista.cz / 2003-06-12 14:29:38 +0200:
> # cox@idecnet.com / 2003-06-11 21:37:58 +0200:
> > From: "Roman Neuhauser" <neuhauser@bellavista.cz>
> > > With DB_FETCHMODE_OBJECT, one does $ret =& new $class, the other
> > > $ret = new $class => different behavior.
> >
> > Of course you haven't tested that. You'll get a marvellouse NULL instead of
> > the object if you change it.
>
> > I don't know if that's the expected behaviour in php, but in that case the
> > change would break DB_FETCHMODE_OBJECT.
>
> I wouldn't have thought this would behave this way, and you're
> right, I didn't test this exact version of the patch. I didn't say I
> did, either.
BTW, here's Andi's explanation of this behavior:
http://bugs.php.net/bug.php?id=2589
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message. see http://www.eyrie.org./~eagle/faqs/questions.html