This content has been marked as final. Show 14 replies
But this is the waited behavior....
I'd say you need at least the ALTER_ANY_TABLE privilege (logical, no?). If that isn't enough to make it work, it might be a bug (report here) or missing feature (report on the SQL Developer Exchange).
I don't agree with ARF. My user has DBA privileges, so he really can edit the table belonging to other users. It appears as if at times SqlDeveloper don't look at the privileges of the connected user, it only check if the user is the owner or not.
Thank you for your input. Best regards
Message was edited by:
Are you access the table through synonyms?
No, I'm not.
Does this matter work ok for anyone? If you connect as system, can you select the "Edit" option for the table of other scheme?
It would be good that any user (even with only the privileges to "see" any object) could have access to all the nice information that "Edit table" shows. What other way do you have, for example, to see all the information about constraints of tables belonging to other users?
No, I'm not.No.
Does this matter work ok for anyone? If you
connect as system, can you select the "Edit" option
for the table of other scheme?
It would be good that any user (even with only theYou can see the constraints currently. You just can't see constraint columns. I believe there is an outstanding bug/enhancement request to show constraint columns in the constraints tab.
privileges to "see" any object) could have access to
all the nice information that "Edit table" shows.
What other way do you have, for example, to see
all the information about constraints of tables
belonging to other users?
The enabling of the "Edit" is being worked on and should be much more accurate when that work has been completed. Sorry for the inconvenience in the mean time.
It seems that edit option doesn't work completely in version 188.8.131.5279
It work for some 184.108.40.206 database but not for 10.2.0.2
Works for me on 10.1 and 10.2.
I suggest you provide Kris all relevant data to be able to track this down: privileges, non default DB parameters, whatever.
The edit option doesn't work in other users. (disabled.)
I do the following test :
1. connect with system (Role dba)
2. select table in "other user"
-> edit option is disabled
3. close table tab
4. select table in my owned object
-> edit option is enabled
2. select table in "other user"
-> edit option is enabled (and work)
(I test it with 9i and 10g and i have same problem)
I activate the debugging but i don't see error for that.
Here my non-default parameters :
nls_date_format YYYY-MM-DD HH24:MI:SS
nls_timestamp_format YYYY-MM-DD HH24:MI:SSXFF
Here my user roles :
I had the same problem when I found this thread. I am running ver. 220.127.116.11.
I was connecting as system and trying to modify a non null constraint on an existing table in an application schema.
The edit button was gray'd out. I grant 'alter any table' priv to system and tried again and the edit button is now usable.
Per MRM direction, I pasted my information from the previous thread I created
Edit option does not display
Here is that info
I did find a thread about this problem, but didn't see a resolution.
Currently, I do not get the edit option for tables, views when selecting a table or view in another schema.
I do get the edit option when selecting triggers. (strange)
I have this problem with multiple databases. 10g and the express edition.
I am able to create, update and alter all tables and views with DDL
I just can't seem to get the edit option to show up for tables and views that I have created in those schemas.
Is there a work around, or a setting that I am missing?
I have loaded SQL Developer 1.2.0 Build MAIN-29.98
Running Windows XP Service Pack 2
As Kris (the application's architect) said in a previous post: it's being worked on.
Maybe we'll have it available in the forthcoming patch (next few weeks), else...
As workaround you can create a connection for the other user, or create synonyms, which make the tables/views available in your nodes.