RE: [metabase-dev] RE: [PEAR-DEV] pearifying metabase: preparing phase 2

Hi, ok next week I will attempt phase 2 which will be to actually use DB.php as a factory to call metabase_database.php and start changing some of the method names and parameters to the PEAR style. I will also add some little stuff like error messaging binding and fetch mode. I will see what else I will have time to do (hopefully Error handling). I will keep an eye that all changes to the metabase code can easily be hidden in the metabase_inferface.php (nobody voted on if they use access the metabase object directly or not ... so I am just assuming I don't have to worry about that) I must admit I was hoping for some more feedback on the stuff I wrote in my last mail (phase 1) .. but so it goes. Something that I would really like to see is a testing suite for PEAR DB so I can be sure that what I do remains compatible with the old PEAR DB. It might not even have to be totally complete as even some tests will make my life easier and my results more reliable. Thomas: you mentioned you had something like this? Especially since my work will not immediately replace PEAR DB this is generally a good idea to have and even a better idea to have if I do not succeed or get hit by a bus :-) One more question: Is the DB_result object really that useful to accept the overhead? I can obviously stick something like that in the final merged version or I can emulate this feature for PEAR DB compatibility mode. What were the reasons to do it (I assume extensibility)? Did they pay off? How strongly does everybody feel about this? Best regards, Lukas Smith smith@dybnet.de _______________________________ DybNet Internet Solutions GbR Alt Moabit 89 10559 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de info@dybnet.de _______________________________