Quoting Toby Thain <[email protected]>: > The Ingres driver has the same 'issue', system tables are returned by > default. I tend to think that no tables should be suppressed from the > result by default when using *this* libdbi function. I think more > input from actual use cases would be needed to see whether anything > needs to be done. >
libdbi is an "abstraction layer", literally, and I tend to think that it should abstract away implementation-specific stuff like system tables by default. This doesn't mean we should make it impossible for users to get at these tables. Nor should we break backwards-compatibility in case some programs rely on the current behaviour. What about providing an additional function called something like dbi_conn_get_user_table_list() which returns only non-system tables, i.e. those usually created by the user or some piece of software? This would allow software linked against libdbi to not be pestered by implementation-specific system tables and such, if this behaviour is desired. regards, Markus -- Markus Hoenicka [email protected] (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ Libdbi-drivers-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libdbi-drivers-devel
