RE: Re: F4 Describe not working via Public Synonym?
John Dorlon <[email protected]>
| Newsgroups | gmane.comp.db.oracle.toad.free |
|---|---|
| Message-ID | <4120B436C765EC43A31CC3E2A13D36A6226BC93B@ALVMBXW02.prod.quest.corp> |
Hi Richard, There are two caches - our connection object does remember a list of tables, and the Editor has a cache for the Code Insight. When you F4 on an object, we check both of these caches, but we do observe the schema name also, so I'm not sure what's going on here. I tried as you suggested with getting USERB's table to show up in the schema browser while logged in as userA, but even when I did that, and F4'ed on USERB_TBL, it worked fine. I also got the table name to come up in the Code Insight popup and F4 still worked after that too. Do you have a default schema set up for that login or were you using the "Current Schema" dropdown in the Editor? Is there more than one object called USERB_TBL in the database? Maybe a synonym called that which no longer resolves to anything? I'm just throwing out guesses here. -John From: [email protected] [mailto:[email protected]] On Behalf Of r_squires Sent: Monday, May 07, 2012 6:10 PM To: [email protected] Subject: [toad] Re: F4 Describe not working via Public Synonym? In order to recreate it (because at first I had the same result as you), I had to refresh the SB LHS Tables tab. I'm guessing this caches a list of tables which the editor uses. I think it's the use of this list that is affecting the F4 functionality. So in your instance, if you refresh the SB LHS Tables list so that your table appears in USERA's list of tables (note, I have the Filter -> Schema Name -> All except Sys selected so not just this users tables are returned*). Then go back into your editor (the table name has probably changed colour to indicate it is recognised) and then F4 you should see the issue I am having. *This would seem like a very likely candidate for the issue I'm experiencing. - actually, I just switched this option off, back to Current Schema Only, and now it's fine so it's definitely that filter option that is causing an issue. --- In [email protected]<mailto:toad%40yahoogroups.com>, John Dorlon <john.dorlon@...<mailto:john.dorlon@...>> wrote: > > Hi Richard, > > I just gave this a try but could not reproduce the problem. I made 2 public synonyms - one with the same name as the object and one as a different name. I could F4 on either one while logged in as USERA without any problems. This is using Toad 11.5.0.56, same as you. Let me know if I set up something wrong. > > Thanks, > John > > create user usera identified by usera; > grant create session to usera; > create user userb identified by userb; > grant dba to userb; > create table userb.userb_tbl as select * from dual; > create public synonym syn_userb_tbl for userb.userb_tbl; > create public synonym userb_tbl for userb.userb_tbl; > grant all on userb.userb_tbl to usera; >