Comments
6 comments
-
Hi Kev,
thanks for posting.
re 1) Personally, I think that '.' should insert in the case of db names, table names etc., but we will make it customisable in version 3. Also, aliases will appear on the candidate list, so hopefully when you type 'J' the alias will be top of the list, so that pressing '.' inserts it.
re 2) No such functionality is planned, at the moment, but I will suggest it for version3. (If others think such a functionality would be a good idea, maybe they could let us know here.)
Also, it will be possible to cache more than one database and to store the schema on disk, which might help in your case.
Regards,
Tilman -
Hi,
Yup, putting the alias in the list occured to me a little after I posted. Much simpler solution. As for caching, that would be good too. At the moment I'm getting used to automatically cancelling the sqlprompt connection window every time I jump on to a remote server to do a quick bit of maintenance
Kev -
I have a similar dev/production situation & ideally I would like to be able to configure SQLPrompt to never connect to certain servers - so that the authentication box never pops up for those servers.
Neil -
Since I'm not the only one now, I'd just add that I'd prefer local gathering to remote gathering with a cache (though I could live with the latter)
-
Another observation. In the example above, the full join would have been something like
ON J.Prefix=L.JobPrefix AND J.ID=L.JobID
ie, the foreign key has two columns. I notice that after I type "ON " sqlprompt offers me two selections : "J.Prefix=L.JobPrefix" and "J.ID=L.JobID". After I type the "AND " the list it offers me is the standard full list of tables in the current database. It would be better if it offered me the list of foreign keys again rather than a full list of tables. In fact, I'm probably missing something here, but why offer a full list of tables at this point at all? Wouldn't it be better to limit it to tables referenced in the query, or at least prioritize them?
Kev -
Hi,
Thanks for pointing out the problem with the foreign keys. We'll look into that.
Regards,
Tilman
Add comment
Please sign in to leave a comment.
1) This one is very irritating, as it results in me inadvertantly inserting incorrect code in such a way that I might not even notice I've done it:
Consider a statement like the following:
SELECT * FROM Jobs J JOIN JobLegs L ON J.Prefix=L.JobPrefix AND
When I type the space after the AND, sqlprompt brings up the completion list as I'd expect, I then type a J (the alias for Jobs) and a '.', and sqlprompt inserts the name of the first table starting with J followed by the '.'. I'd prefer it if there were an option to specify what keypress would accept an intellisense suggestion. At the moment this is likely to be a showstopper for me.
2) All of our production databases also exist in more or less the same state on our development server. It would be useful if we could always have the intellisense metadata gathered from the development server rather than the production server, particularly as our production servers are mostly at remote sites, and metadata gathering is slow. Ideally I'd like the system to let me specify a list of database names to map onto a single metadata source.
For example, if we had a development database 'Test', which had the same schema as the remote databases 'TestVT3' and 'TestMTL', and I opened a query window on TestVT3 or TestMTL, then I'd like it to go to 'Test' on the local server for metadata.
I realise that there are sync issues here, but for me they'd be easilly compensated by the faster metadata gathering
Kev