Show more/ other view context information
Brought to you by:
ansgarbecker
Originally created by: lutz.thi...@gtempaccount.com
In old versions (e.g. 2415) HeidiSQL column information (names, data types
etc.) was available for views (see screen short ss_1.gif).
In latest HeidiSQL version only some "create view" information is available
(not to much useful for my daily work, see screen shot ss_2.gif)
How about adding multiple sub tabs like it is already available for tables
(see screen shot ss_3.gif)?
- Basic (column information)
- create code
- alter code
Thanks & Regards,
Lutz
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: a...@anse.de
Not sure if sub tabs are the way to go. However, for what purpose would you list the
columns? You cannot edit them anyway - it would just be a readonly list.
Status: NeedInfo
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: lutz.thi...@gtempaccount.com
In case, if a view contains a large number of columns and you'd,like to known the
exact names (e.g. to create a query), it's nice to see all column names and its types
in well structured vertical table similar to a database table.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: a...@anse.de
You noticed that columns of views are listed in the right hand query helpers box?
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: lutz.thi...@gtempaccount.com
In principle you are right, but there is no column type information...
Furthermore, from a user perspective it is more handy to have a similar behavior for
tables and views...
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: a...@anse.de
> it is more handy to have a similar behavior for tables and views
Yes - but if we're talking about the query editor, it *is* exactly the same for
tables and views.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: a...@anse.de
Again the question: What is a practical use case to have such a readonly list in a
view editor?
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: lutz.thi...@gtempaccount.com
From a database administrative point of view you are right.
But if you use HeidiSQL as THE tool to write queries and you need to know the data
types of the columns of a view in a quick and easy way, it is much more handy to have
the same usability for tables and views...
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: a...@anse.de
For query writers it doesn't help much to have a list on another tab than the current
one where the query is.
HeidiSQL also pops up with an auto completion pulldown when you type something like
SELECT * FROM myview.
or
SELECT * FROM myview AS m WHERE m.
... and displays the columns of the view, including data types. See the screenshot.
That should be very helpful isn't it?
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: lutz.thi...@gtempaccount.com
I give up... ;-)