Comments
2 comments
-
Hi,
Thanks for posting. I'm afraid I can't reproduce your problem. Or maybe I don't quite understand what you are after.My problem is that when I connect using user A that is the owner of schema A, I need to refresh the cache explicitly by using the cache management.Howver, when I change connection, I can see that SQLPROMPT is refreshing the cache. My question is why do I need to refresh the cache when I change form connection to another?
Regards,
Tilman -
My problem is that when I connect using user A that is the owner of schema A, I need to refresh the cache explicitly by using the cache management.
[/quote]
I need to refresh the cache explicitely because the candidate list does not show the tables related to schema A. It shows whatever candidates tables were in the cache. If the cache contained tables from schema B, they would appear in the candidate list. Since I switched connection to user A and the only objects available to him are the one in schema A, I would like the candidate list to show me only schema's A objects. The only way I can achieve it right now (latest 3.0 refresh version) is to manually refresh the cache. Since SQLPROPMPT refreshes the cache when I change the connection, why it doesn't show me the current connection related objects?
Thank you!
Thank
Add comment
Please sign in to leave a comment.
Thank you,
Ccote