Hello, On 01/30/2003 02:48 AM, John Wells wrote:
If you are concerned about speed, I think you should not bother to use a database wrapper because all of them add overhead due to the flexibility they provide. The more is the flexibility, the more overhead may be added.Trying to decide between wrappers for a rather large application, and wanted some input from the group as I haven't used any of these to any degree. So far, I've found PearDB, metabase, adodb, and MDB.What's the best option? My main concerns are speed and good community support.
If on the other hand you are looking for database application portability so you do not have to rewrite your application if you switch databases, maintainability and thus development speed, you may want to try Metabase or MDB which is a Metabase version with PEAR-DB like API.
Metabase lets you write truely portable database application. Other provide some level of portability but not up to the level that Metabase provide.
One unique feature of Metabase is that it provide very easy and portable database schema management. This means that in practice you can easily describe your database schema with tables, fields, indexes and sequences in a very XML based format and Metabase installs the schema for you.
Later, if you want to change your schema by adding/removing/altering any of the schema objects, you can simply alter the schema definition and Metabase will apply the changes without affecting any data inserted after the database schema was installed for the first time or updated for the last time.
Furthermore, if you are looking for very fast database application development support, you may also want to look into Metastorage. This is a database API generator application that lets you model your database applications in the form of classes of objects that basically wrap around your database tables providing functions that you specify that your application need to manipulate the table rows as objects of such classes.
All you need to do is to specify in a very simple XML format, the classes with the variables you need, validation rules, relationships between classes and the functions of the operations your application needs, and Metastorage generates all the code of the classes for you, including the code to install and maintain the database schema.
For now, Metastorage generates code based on Metabase but in the future it will generate compatible code that just uses calls to the native database PHP API functions, thus achieving maximum speed as you need while also assuring true portability.
Either Metabase and Metastorage are integrated in the same project repository that you may learn all about it here:
http://www.meta-language.net/
--
Regards,
Manuel Lemos
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
