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

Request #10849 Remove DB_Storage
Submitted: 2007-04-26 21:17 UTC
From: dufuz Assigned: dufuz
Status: Closed Package: pearweb (version 1.14.0)
PHP Version: Irrelevant OS:
Roadmaps: 1.15.0    
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:
Solve the problem : 14 + 38 = ?

 [2007-04-26 21:17 UTC] dufuz (Helgi Þormar)
Description: ------------ The idea is to remove PEAR_User and PEAR_Package that both extend from DB_Storage, since it's only a half way DBDO kind of class then we should just do this our selfs and thus loose this dep and be one step closer to moving to MDB2 or PDO


 [2007-04-26 22:38 UTC] dufuz (Helgi Þormar)
I'm done killing of PEAR_User, indcidentally I had to create PEAR_Auth class to keep the is/isAdmin/isQA/makeLink function and also add a data() function to make the user data array into an object so $auth_user can still work as it did (we really should change that thing tho) Also I made user::info a tad more flexible, the ability to return passwords (not for XMLRPC of course) so that account-edit would still work and such. on top of that I didn't see why xmlrpc should be able to call user::remove so I removed the proto for that, any objections to that ? So on to the new beast, PEAR_Package :-)
 [2007-04-26 22:49 UTC] dufuz (Helgi Þormar)
And voila, PEAR_Package is gone, probably the most useless thing I've seen in pearweb by far and was only causing loads on package-info.php to use a simple function and a little data fetching.
 [2007-04-26 22:54 UTC] dufuz (Helgi Þormar)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.