Comments
Sort by recent activity
Tilman wrote:
I wrote:
And while you're at it, a way to sort by other columns would be great.
Could you explain this a bit more?
A common (but not universal) UI pattern in Windows is that in grid or listview-type controls, the columns have headings. When the heading of a particular column is clicked, the list gets sorted by that column. A second click changes it to a descending sort. And for bonus points, control-click adds another column as secondar (or n-ary) sort criteria.
Although the way you currently have the list organized is probably correct for most cases, there are times when an alternate sort might be useful.
For example, in the Columns from all tables list, the default sort seems to be column name. However, the containing table name (i.e., the right column) might make sense if I know where the column is, but not its name. / comments
Tilman wrote:
I wrote:
And while you're at it, a way to sort by other columns would be great.
Could you explain this a bit more?
A common (but not universal) UI pattern in Windows is that i...
Regarding (e), I now see that there is a resize grabber. I'd swear there wasn't one there before, but I can't reproduce that. / comments
Regarding (e), I now see that there is a resize grabber. I'd swear there wasn't one there before, but I can't reproduce that.
I have to disagree. I'm working in Query Agonizer, where it doesn't pop up at all.
I'm not a DBA; most of my work is in .Net code, but I do a ton of DB work as well. I'm used to the way VS.Net's intellisense pops up, which is intrusive. Like it or not, this is the mode that most users like me will be used to. / comments
I have to disagree. I'm working in Query Agonizer, where it doesn't pop up at all.
I'm not a DBA; most of my work is in .Net code, but I do a ton of DB work as well. I'm used to the way VS.Net's in...
nanchen wrote:
for me, there is no need for an option: intellisense should not work inside comments!
I disagree. A common pattern for me, and some of my coworkers, is to use comments as a defense against premature execution of a data-changing query.
I'll frequently do something like
SELECT * FROM mytable
-- UPDATE mytable SET x=y+1
WHERE z IS null
The idea here is that I can verify that my query targets the right rows by running it as shown. Then I select the bottom two rows (except the "--") in order to make the actual change.
In this situation I don't want to uncomment the UPDATE because that eliminates my protection. But I would like the intellisense help for that part of the query. / comments
nanchen wrote:
for me, there is no need for an option: intellisense should not work inside comments!
I disagree. A common pattern for me, and some of my coworkers, is to use comments as a defen...
Regarding the presence of system objects in the list, I initially thought the same thing. But in real life, it seems that they don't actually interfere with "real" objects. So far, I've always had it come up zeroing in on the directly applicable stuff, with the system objects a long way off in the list.
Regarding aliases, I rather like the automatically-generated abbreviations. Of course, that's probably because I tend to create my own aliases in exactly that way [image] / comments
Regarding the presence of system objects in the list, I initially thought the same thing. But in real life, it seems that they don't actually interfere with "real" objects. So far, I've always had ...
I like the idea of an alternate tabular representation.
Some of the stuff displayed gets rather large, though, and hard to see in any meaningful way. I notice first that the extended properties (which I try to use to document tables and columns) get ridiculously wise; some of the other lines, like constraints, are wide as well. Perhaps some kind of wrapping could be allowed in these cases.
What if this display were interactive? Imagine double-clicking on an object name in the information panel, and have that object become selected in the candidate list?
This would allow the user to locate the target not just by scrolling through categorized lists, but by actually navigating through the structure of the database! / comments
I like the idea of an alternate tabular representation.
Some of the stuff displayed gets rather large, though, and hard to see in any meaningful way. I notice first that the extended properties (wh...