From: Chris D. <cdo...@cc...> - 2004-06-30 14:27:57
|
Ben and Yves, Thanks for your warm responses. I agree that the lack of users listed on the libdbi website doesn't look particularly promising however, I think it is probably the correct direction to go, assuming that we don't run into performance issues that require customized database code. A company that I work for, uses the perl package DBI for all of our web applications that interface with databases. I don't believe that DBI for perl and libdbi are related except that they serve the same purpose for their respective languages. Based on an initial comparison of the MySQL code in PerfParse 0.10 and the MySQL dbd module for libdbi, It doesn't look particularly difficult to change from the current MySQL specific calls to libdbi calls. Has the database interface code been changed significantly for 0.11? I would like to propose the following plan of action: 1. Produce a patch for 0.11 which enables a configuration option to use libdbi in stead of direct MySQL code. (MySQL code is still default) 2. Role the patch into the 0.12 release 3. Down the road (0.13 or later), make libdbi the default and MySQL an option. 4. Much farther down the road, we can remove the MySQL option all together (or not). All of this is dependent on getting reasonable performance using libdbi. If libdbi is unusable, I will scrap it in favor of writing code for each database. If it is usable but not as good as MySQL directly, we just might not ever make it to steps 3 and 4 above. Let me know how this sounds and I am anxiously awaiting the release of 0.11. Chris |