That's fine. I'll revert it. But I think the previous issue was that it was also returning indexes as well. I'll just narrow down to tables, views, and mat views
On 15 October 2015 at 17:39, Thomas Kellerer <spam_eater@gmx.net> wrote:
All I can say is, that due to the nature of SQL Workbench (being DBMS independent) I do use (or at least test) many other DBMS and every[1] other JDBC driver does return view columns - including materialized views in Oracle and DB2.
So apparently all the other vendors think it makes sense to return view (and materialized view) columns.
Thomas
[1] I have tested at least briefly more than 15 different ones.
Dave Cramer schrieb am 15.10.2015 um 22:47:
So I am looking at the API reference and no where does it say getColumns should return information about views.
That being said the fact that getTables returns the type of the table there may be some inference that it should ?
* fix: filter DatabaseMetaData.getColumns by tables PR #386 (0c95126)
Why was this done?
From my perspective this is a serious bug, because now getColumns() doesn't return column information for views, materialized views or foreign tables any more.
Which in turn means that the SQL client I am maintaining (SQL Workbench/J) is no longer able to display column information for anything else than tables.
I would assume that this is true for any other JDBC based SQL client. It will also break tools like Liquibase and probably Hibernate as well as they also rely on getColumns() to return information about views (I am sure about Liquibase, not 100% sure about Hibernate though)
