Suggestions drop as name typed

MikeyC

Given this code:

USE msdb;

SELECT 
	backu<cursor>
FROM dbo.backupfile A

It suggests: backup_set_id, backup_size, and backupfile, etc..

Backupfile is the table and is aliased as A so it isn't a valid suggestion.

If you type the next character leaving this code:

USE msdb;

SELECT 
	backup<cursor>
FROM dbo.backupfile A

There are no fields suggested, the suggestions start with backupfile, which is a table and again isn't valid because it has been aliased, and the other tables aren't valid because they aren't included in the FROM clause.

I am using SQL Prompt 4.0.2.53. (And it appears that 3.9.x suffers from the same problems.)

Anu D

Many thanks for your post.

It works fine for me!

Can you kindly check the following option is selected or not?

SQL Prompt 4 -->Options --> Suggestions --> Types of Suggestion --> Select 'List all database columns after a SELECT statement'

Please let me know whether it makes any difference.

MikeyC

I do not have that option selected, and I wouldn't want it selected because it would include invalid selections.

I turned it on, and when it was one the columns were suggested.

What I noticed is with the option turned off when I just have "backu" typed it properly lists the columns, when I add the "p" the columns go away, but then if I type a "_" the columns come back. Maybe it has to do with "backup" being a reserved word or something?

Anu D

Yes you are correct it is because Backup is a reserved word.

Kindly let me know if you have any other questions regarding this product.

MikeyC

Is this something that will be fixed in a future version? (I wouldn't think field names that start with a reserved word should cause a problem.)

MikeyC

I see this wasn't fixed in 4.0.3... I, also, noticed you didn't mention a assigned tracking ID. Are you not going to fix this?

Chris Auckland

I'm very sorry we didn't update you with the bug tracking number for this.

It is something our developenet team are aware of. For your reference the bug tracking code for it is SP-2648.

It has been approved to be fixed in a future version, but at this stage I can't give you a timeframe for when you can expect it.