Activity overview
Latest activity by bis
I am indeed using 3.0.0.868.
I can reliably reproduce the problem with the join, like so:
create table A(a_id int not null primary key)
create table B(b_id int not null primary key)
create table C(c_id int not null primary key, a_id int not null foreign key references A(a_id), b_id int not null foreign key references B(b_id))
-- update the SQL Prompt cache
select *
from C c
join A a on c.a_id = a.a_id
join B b on [completion list does not include the join from C to B]
The behavior of SQL Prompt with regards to multi-column foreign keys strikes me as being an optimization for the uncommon case. Yes, on rare occasions I only want to join on some of the key columns, but I would by far prefer to have SQL Prompt spit out the full relationship and then delete the unwanted conditions myself to SQL Prompt making me cursor around the completion list every time I want to make the normal join. / comments
I am indeed using 3.0.0.868.
I can reliably reproduce the problem with the join, like so:
create table A(a_id int not null primary key)
create table B(b_id int not null primary key)...
when is 3.1 coming?
This release still includes bugs that I and others have brought up previously:
The candidate list interferes with typing table aliases and SQL keywords ("where", "order by", "group by", etc)
No fo...
The resizing is helpful to know about - I had noticed it before, but it didn't come to mind when I was in the middle of typing a query. Besides, I type fast enough that I might as well just finish typing the whole long column name rather than moving my hand to the mouse and resizing some window.
Visual Studio's solution, which I like, is to use a smaller variable-width font (MS Sans Serif, I think) instead of using the normal editor font.
I am sure that you wouldn't want to delay the release of SQL Prompt 3 to rewrite the candidate list display code, but I think it would be a great feature for 3.5. / comments
The resizing is helpful to know about - I had noticed it before, but it didn't come to mind when I was in the middle of typing a query. Besides, I type fast enough that I might as well just finish...
long column names in the candidate list are truncated
The candidate list truncates column names longer than 15 characters down to 13 characters. Compare this to the behavior of Visual Studio, which happily displays the full text of such long class na...
error when opening two Query Analyzer windows
When I open two Query Analyzer windows in rapid succession, the first window opens correctly and starts loading, but when the second window opens, I get an error:
Unhandled exception has occurred ...
update query with table alias confuses SQL Prompt
If I try to type an update statement that uses a table alias, SQL Prompt behaves quite badly. For instance, if I type this query to look at the rows that I want to modify:
select *
from Foo f
join...
Candidate list captures Home and End
When the candidate list is displayed, SQL Prompt captures the Home and End keys, using them to move to the top and bottom of the candidate list, respectively. Visual Studio's Intellisense does not...
Here's a quick history of how computers have been punching me in the eyes (or not) with their color schemes:
The Commodore 64, which had light blue text on a darker blue background - very easy on the eyes
The Apple II, which had white text on a black background - also very nice to look at. (except for the weird color fringing around the edges of characters due to Apple's before-its-time sub-pixel rendering.)
MS-DOS. Light gray on black. So soothing.
Turbo Pascal, WordPerfect, MS Word, and many others for DOS: white or yellow text on a blue background. Very easy to read. (And Turbo Pascal 7 had syntax highlighting!)
Windows 3.x, 9x. Black text on a white background by default, which portends much. But at least it's easy to change to white-on-black.
AutoCAD: white lines on a black background by default.
Emacs: Has 'light' and 'dark' settings as well as complete customizability. I use 'dark'.
Visual Studio and Query Analyzer: follows Windows' color scheme, and allows all of the syntax highlighting colors to be customized.
Red Gate SQL Prompt: sometimes follows Windows' color scheme, sometimes not. This is very much in keeping with new versions of Windows, Office, and many other applications.
I don't need white-on-black, but if I have to stare at a glorified light bulb all day, I want it to be as dim as possible, and that's what white-on-black does.
Here's a discussion on the topic: http://cafe.elharo.com/ui/black-on-white-good-white-on-black-bad/ / comments
Here's a quick history of how computers have been punching me in the eyes (or not) with their color schemes:
The Commodore 64, which had light blue text on a darker blue background - very easy on ...
various quirks
I've been playing around with various things that didn't work as I expected in SQL Prompt 2 to see what has changed in 3. The new version is definitely a step up, and would be close to perfect, wi...