Re: mdb2 game plan

Lukas, This is an *awful* lot of packages, and as you say there could be more drivers. Perhaps you could setup a channel server for the drivers? :) Use install groups for the drivers like this: $ pear install MDB2#mysqli etc :) - Davey Lukas Smith wrote:

Hi, ok so here is the game plan .. with the next release I will split off MDB2 into the following packages: MDB2 - 2.0.0beta4 beta MDB2_Extended - 0.1.0 beta depends on MDB2 2.0.0beta4 MDB2_Schema 0.1.0 beta (used to be MDB2_Tools_Manager) depends on MDB2 2.0.0beta4 MDB2_Driver_mysqli - 0.1.0 beta depends on MDB2 2.0.0beta4 MDB2_Driver_mysql - 0.1.0 beta depends on MDB2 2.0.0beta4, MDB2_Driver_mysqli 0.1.0 MDB2_Driver_pgsql - 0.1.0 beta depends on MDB2 2.0.0beta4 MDB2_Driver_ibase - 0.1.0 beta depends on MDB2 2.0.0beta4 MDB2_Driver_oci8 - 0.1.0 beta depends on MDB2 2.0.0beta4 MDB2_Driver_sqlite - 0.1.0 beta depends on MDB2 2.0.0beta4 MDB2_Driver_mssql - 0.1.0 alpha depends on MDB2 2.0.0beta4 MDB2_Driver_fbsql - 0.1.0 alpha depends on MDB2 2.0.0beta4 MDB2_Driver_querysim - 0.1.0 alpha depends on MDB2 2.0.0beta4 not sure yet what to do about the peardb wrapper. i will also keep the lob and the date class in core. i dont think that many people used it anyways but i guess it will stay in core for now regards, Lukas