Re: TableInfo (was:Package Proposal : DB_Dump)
| From: | indyone :o\) | Date: | Wed, 04 Jun 2003 01:21:29 +0000 |
| Subject: | Re: TableInfo (was:Package Proposal : DB_Dump) | ||
| References: | 1 2 | Groups: | php.pear.dev php.pear.dev |
| Request: | Send a blank email to pear-dev+get-16977@lists.php.net to get a copy of this message | ||
Lukas Smith wrote:
So you are thinking that if i develop this class having in mind to support more than one database, and also try to improve the DB::tableInfo(), as this will be the way i'll get the informations for each db table, would worth this project to belong in PEAR? So would you think to start and improve this class, and when i have a stable version, then i will re-propose it in this mailing list...? +----------------------------------------------------------+ | Software Failure. Press left mouse button to continue. |From: Bertrand Mansion [mailto:bmansion@mamasam.com] Sent: Sunday, June 01, 2003 1:44 PM <smith@backendmedia.com> wrote :withMDB already has a portion of these things available and hopefullycurrentlythe next version of MDB things will become more flexible, assothings are very focused on maximum portability. So maybe MDB might become a worthwhile alternative for this project. Anyways tableinfo can certainly be improved to make it possible to support enough features/data structures to make it worthwhile for a large number of people. It doesn't have to solve every possible situation where you might want a dump, it just needs to solve enoughbecausethat there is an added value over phpMyAdmin. Maybe even the same functionality as phpMyAdmin with PEAR CS would be a value addediirc the phpMyAdmin code is very nasty(?)
| Guru Meditation #00000025.65045338 |+----------------------------------------------------------+