Activity overview
Latest activity by dm
It was both in the candidate list and in the inserted text (after typing ON).
If you do show both related and unrelated tables after JOIN then perhaps show the unrelated tables in a different way (slightly different icon) .. although I'd prefer to have an option not to see the unrelated tables since they are irrelevent for the databases I work with.
Bart Read wrote:
Hi there,
Thanks for posting. Glad it's working OK for you on Vista: it's one of the things we wanted to get properly sorted out for 3.1. The final 3.1 release should be available in the next couple of days which fixes a seriously annoying case-sensitivity bug when filtering objects by owner/schema.
dm wrote:
* After hitting JOIN I really want it to just show me tables related via a foreign key -- in 99.9999% of the time those are the tables I am interested in
That's fair. In fact we had somebody else ask about that a few days back. I'm sure we'll be adding that at some point in the future, although what we'll probably do is just show those tables at the top of the list rather than only showing them. With SQL Prompt 2 we had some complaints that you could ONLY see such tables, hence we derestricted the list but with everything else we had to do we didn't have time to refine the functionality further.
dm wrote:
* The tables on the inserted ON are prefixed by the schema, even though I've removed that option in the Options.
Is this just in the candidate list or after you've actually inserted the join condition into your script? Either way this sounds like a bug.
Thanks,
Bart
/ comments
It was both in the candidate list and in the inserted text (after typing ON).
If you do show both related and unrelated tables after JOIN then perhaps show the unrelated tables in a different way (...
3.1 Feedback
Hi there,
I've just downloaded and installed 3.1 on Vista --works well!
A couple of small initial issues:
* After hitting JOIN I really want it to just show me tables related via a foreign key -- i...
There are even more fun cases such as tables called [ ] or even
[
]
I'm not sure you deserve intellisense if your table/column looks like this: [ ].[
]
:-) / comments
There are even more fun cases such as tables called [ ] or even
[
]
I'm not sure you deserve intellisense if your table/column looks like this: [ ].[
]
:-)
One reason that it can appear to work intermittently is that version 2 only looks at the text before and after the cursor that is delimited by blank lines ... so ensure that your current SELECT has a blank line before it... / comments
One reason that it can appear to work intermittently is that version 2 only looks at the text before and after the cursor that is delimited by blank lines ... so ensure that your current SELECT has...
A common reason for it to appear to stop working is if there are blank lines in the current query.
SQL Prompt 2.0 only looks at the chunk of text in the editor around the cursor that is delimited by blank lines ... / comments
A common reason for it to appear to stop working is if there are blank lines in the current query.
SQL Prompt 2.0 only looks at the chunk of text in the editor around the cursor that is delimited b...
Try removing the blank lines -- the parser did (does?) just handle the chunk of text around the cursor that is delimited by blank lines. / comments
Try removing the blank lines -- the parser did (does?) just handle the chunk of text around the cursor that is delimited by blank lines.
You might want to take a look at the "Candidates" Options tab -- you can enable the use of schemas there for 2005. / comments
You might want to take a look at the "Candidates" Options tab -- you can enable the use of schemas there for 2005.
There is an option under "Candidates" to make it show joins based on matching column names ...
HTH / comments
There is an option under "Candidates" to make it show joins based on matching column names ...
HTH
The parser in 2.0 requires that the SELECT that your FROM is part of should be delimited by blank lines.
This won't work:
EXEC SomeSP
SELECT * FROM <Ctrl-Space>
This will:
SELECT * FROM <Ctrl-Space>
Hope this helps. / comments
The parser in 2.0 requires that the SELECT that your FROM is part of should be delimited by blank lines.
This won't work:
EXEC SomeSP
SELECT * FROM <Ctrl-Space>
This will:
SELECT * FROM <Ctrl-Space...
Hit TAB after the *, as in
SELECT *<TAB> FROM Orders
Also:
SELECT o.*<TAB> FROM Orders as O / comments
Hit TAB after the *, as in
SELECT *<TAB> FROM Orders
Also:
SELECT o.*<TAB> FROM Orders as O