Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.11.5

Bug #603 add BC option for clear _query on fetch()/find()
Submitted: 2004-01-20 12:01 UTC
From: pear at l2gx dot net Assigned: alan_k
Status: Closed Package: DB_DataObject
PHP Version: 4.3.4 OS: Mac OS X
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 30 - 22 = ?

 
 [2004-01-20 12:01 UTC] pear at l2gx dot net
Description: ------------ If I'm correct, the default behaviour of the latest DB_DataObject version is to clear $obj->_query on fetch(). This behaviour gets my current codebase into serious trouble. Is there any option to set to prevent this, effectively returning to the original behaviour ? I need the $obj->_query settings to proceed on related objects/ tables, so to solve this until there is a better solution I have to do: function fetch() { // to circumvent clearing of _query at fetch() $query = $this->_query; $result = parent::fetch(); $this->_query = $query; return $result; } I believe ther has been a config option for this...

Comments

 [2004-01-24 07:26 UTC] alan_k
This bug has been fixed in CVS. In case this was a documentation problem, the fix will show up at the end of next Sunday (CET) on pear.php.net. In case this was a pear.php.net website problem, the change will show up on the website in short time. Thank you for the report, and for helping us make PEAR better. keep_query_after_fetch = 1