On Monday 01 January 2007 09:19, Ed Leafe wrote: > On Jan 1, 2007, at 12:13 PM, sheila miguez wrote: > >> Also I have to admit that I could add the features to the > >> dbPostgres.py and > >> just make them available to the programmer. > > > > I think if it's something many programmers would want then there > > should be some sort of interface for all of the database classes to > > implement so that everyone doesn't end up reproducing this in a > > million different ways everywhere. > > Why not add a chart to the Wiki where people can brainstorm and > compare the various backends? > > Also remember that Dabo is not intended to be a replacement for DBA- > type tools; it is intended to present a consistent way of interacting > > with data for an application developer. From John's last post: > > 5. CLUSTER , VACUUM , and EXPLAIN are features unique to POSTGRESQL. > > These are good examples of what I don't think belong in Dabo. You > can certainly access them via cursor.execute(); anything that can be > executed from a script or command line will work with execute(). But > that doesn't mean that we need a dCursorMixin.vacuum() command. > > -- Ed Leafe > -- http://leafe.com > -- http://dabodev.com > > > > _______________________________________________ > Post Messages to: [email protected] > Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
I like the idea of creating a list on the wiki. It may help determine what (if any) special features are worth while to include. Just to be clear. I did include "CLUSTER , VACUUM , and EXPLAIN" and several others. But I don't believe they have any business in Dabo. My point was only to bring attendion the many features of database engines Dabo does not use to it's advanage. And please recall that this nothing more than a suggestion that started with a question on Dabo features. -- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
