Comments
1 comment
-
Absolutely. What I'm going to add for the final release is an option, that will be on by default, which allows this to happen.
Now, the reason it needs to be an option is memory usage. For small, and even moderately sized databases it's no big deal, but for very large databases problems are likely to occur due to the data structures we use to keep the candidate filtering so fast. At the moment filtering is O(1) on each keypress regardless of whether you have 100 candidates or 100,000 in the list, but that kind of performance comes at a price, and for schema based filtering the price is that we need to build up lists that are prefiltered by schema. This means using more memory. As I say, not really a biggy for small to medium sized databases, but if you've got more than 100,000 objects you're probably going to want to switch this off.
The other thing is that in the final release you can just type the name of the object, skipping the owner entirely, and then select the right one in the candidate list (there may only be one match anyway) and the name will automatically be qualified with the owner/schema if you have the option set.
Thanks,
Add comment
Please sign in to leave a comment.
select *
from schemaName.
The list needs to be filtered to only objects in that schema, otherwise I still have to hunt through tons of objects (including sys. objects, which was what I was hunting through)