Problem description: Currently, the main window parts in four sections (or rather 5): 0. Database |1.Tasks | 2. Description Tables |_______________________________ Queries |3.Tables | 4. none/document ... This is about the 4th section, by default set to "none" (no further lable), but changable to "document" (rather content? - retranslated from German). Expected behavior: I'd like to utter my wish to add further views on tables, namely "properties", which could present some core information (amount of data rows, size, last change, date of creation ...). As I tend to forget names of tables, I'd even prefer, to have access/change dates displayed directly in 3. next to each table name. Any chance to get parts of this implemented, one day? Cheers Mike Operating System: Debian Version: 4.0.2.2 release
@Lionel - seems reasonable to me but want to make sure it's a valid request.
I understand the legitimacy of the wish. If someone feels like implementing it, I take patches. Stuff we can IMHO reasonably achieve show there: Number of rows: get it from "SELECT COUNT(*) FROM tblName" or XDatabaseMetadata::getIndexInfo (from the row with TYPE=tableIndexStatistic) Structure of table and its indices: columns, column size, type, ...: XDatabaseMetadata::getColumns and XDatabaseMetadata::getIndexInfo Table privileges: XDatabaseMetadata::getTablePrivileges Stuff that is far more difficult: creation date, byte size of the table, date of last change, ... The reason is that AFAIK there is no well-established API for getting this information. I expect many database systems don't even track / store / remember the creation date or date of last change. Theoretically, we could add a new SDBC interface to give this kind of information, but then we have to implement for each SDBC driver, which is not that bad, but the worse is that it will "never" work / be available for access through ODBC nor JDBC, since neither ODBC nor JDBC have an API call to get this information. And obviously it will only work for DBMS that actually track these informations, and expose some kind of way to get the information (e.g. a system-specific SQL query).
Adding self to CC if not already on