How can we help you today? How can we help you today?

Not very smart on typed prefixes in general....

I just noticed SQL Prompt 3 doesn't seem to be very smart about pre-typed prefixes, either....

So I have a query like

select * from dbo.T_Contract as c

and then I go back to specify a few fields from the contracts table, and I have

select c.<cursor> from dbo.T_Contract as c

and when I press Ctrl-Space there, I get the list of fields in the T_COntract table as expected.

Selecting a field however results in this query:

select c.c.ContractID from dbo.T_Contract as c

which is obviously not good.

I wish SQL Prompt 3 could be smarter about seeing whether or not I've already typed the dbo. prefix on table and views, or a table alias prefix on a column, and *not* duplicate it, if already present!

Thanks.
Marc
mscheuner
0

Comments

3 comments

Sort by
  • Bart Read
    Hi Marc,
    Thanks again for this. Please see my post in reply to your topic about owner/schema names: the same thing applies. We just didn't have time to fix this for the beta.
    Cheers,
    Bart
    Bart Read
    0
  • mscheuner
    Bart Read wrote:
    Please see my post in reply to your topic about owner/schema names: the same thing applies. We just didn't have time to fix this for the beta.
    Thanks - yes, I noticed a "known issue" in the release notes, too, later on. Hope it'll be fixed in Beta 2! :-)

    Marc
    mscheuner
    0
  • Bart Read
    No problem. It *is* very annoying. We'd just reached the point where we needed some feedback because the somewhat "different" nature of the candidate list was a bit of a risk and we didn't know what people would make of it.
    Thanks,
    Bart
    Bart Read
    0

Add comment

Please sign in to leave a comment.