Comments
Sort by recent activity
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.
Why do you need to refresh the cache? Has the schema changed? Is the candidate list empty?
[/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 / comments
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.
Why do you need to refresh the cache? Has the...