NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
2 replies Latest Post - 2012-12-09T04:40:06Z by XiLong
Pinned topic Use column descriptive info (comment or label) in SQL result view
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Current SQL result page is using column name in the table header, is it possible to use column description (either column comment or column label) in the table header? The column name may be meaningless, only column description (column comment or label) could tell what's the data in this column.
Updated on 2012-12-09T04:40:06Z at 2012-12-09T04:40:06Z by XiLong
vpetrill 0700000NDM21 PostsACCEPTED ANSWER
Re: Use column descriptive info (comment or label) in SQL result view2012-12-06T16:29:58Z in response to XiLongI think this is a very good suggestion. I would like to ask if we could do this in a different way while still meet your needs. Have you looked at the feature launched by right clicking on a table in the Object List Editor and selecting Data->Browse (or Edit) Data. It is more graphical and it is possible to display more information like this when hovering over the column headers. There has been some discussion on adding more features into the data browser/editor and using it in more places, leaving the SQL results view to provide general results of operations rather than support general data querying.
XiLong 060000K1MJ3 PostsACCEPTED ANSWER
Re: Use column descriptive info (comment or label) in SQL result view2012-12-09T04:40:06Z in response to vpetrillMost DB2 i developers are used to "Select * from ..." then press F4 to promot for column names and where clause to construct a completed SELECT statement. So SQL result view will be mostly used.
For the option to display data by Data -> Browse, if we could provide the function to input WHERE clause, they will very helpful. In real case, each table may have a huge amount of rows, the browse function need to improve the usibilty.