Comments
3 comments
-
Hi Esio,
I've added a suggestion to our list.
Thanks,
Tilman -
Hi Tilman.
Another question.
I was using QA, using a specific login user (windows login).
Then, for a specific reason, I needed to open a second window, in the same server/database, but using another sql login.
SPv3 than started getting the schema again. The same schema I think.
I'm presuming you are not checking the permissions wich user have in database (I tested this, SPv3 bring me a table in intelissense that my user don't have permission). So, why is it necessary do get the schema again?
Another question, is, maybe can be a good idea, when opening a new widow, a dialog box asking if the user want's to use intelissense in this windows. I think in SQL Prompt 2 it's work.
In the sample above, I needed to disable SPv3 and open a new QA application with the second user.
Thanks
Ésio Nunes -
Hi Esio,
That's correct. At present we don't check user permissions when retrieving meta-data. There are a variety of reasons for this, mainly because we're using a meta-data model that we use in a variety of other products and to some extent it's a black box. If we hadn't done this SQL Prompt 3 wouldn't ship until the middle of 2007 at the very earliest. As such we've had to live with a few limitations in this model because we haven't had time to do the additional work outside of the meta-data model ourselves.
This is one of those cases. The choice to pull back the meta-data again when different login credentials are used makes sense in that different users have a different view of the database, however at present we don't check the permissions (as you've observed), and due to a limitation in the model it's likely not to work unless the user in question has dbo privileges anyway. This is something we're planning to correct in the near future, although probably not in time for the final release of SQL Prompt 3.
Thanks,
Bart
Add comment
Please sign in to leave a comment.
Accidentally I clickec Refresh all in Cache Management box. I take's me a long time. I pressioned this by mistake, I was found only one database refresh.
Maybe can be interesting a button "Cancel Refresh" for case like this.
Thanks
Esio