Lukas Smith wrote: > With overhead I mean you have a another object that first > builds the query that in turn creates a DB abstraction > layer object ...
There is more to layer 3 than you imply here, especially if you venture on into the land of user interfaces represented by objects and coupling these with your query generation layer. Representations of Transactions, Query and Attribute Caches, eager and lazy retrieval strategies (Strategy Objects), and a modelling application come to mind immediately. Again, see Apple WebObjects and .NET for ideas. Ideally, for standard applications such as table browsing and editing, master-detail relationships and simply "update form and commit" interfaces, the same code should be able to connect to a weblike GUI and PHP GTK as well as to PHP with a Qt Interface by simply switching or reconfiguring some factory classes. That would cover about 80% of all database applications with a GUI by simply connecting a few classes and setting delegates to your application class for the basic logic. Kristian -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
