|*Development Comment <p>Use a trigger* And what if we want to avoid triggers?||10||04-JAN-16|
|Absolutely would love to see this. Very handy, quick, very useful, otherwise have to have to constantly set sql to set schema, but then it's misleading what schema you're in at that point, not very intuitive. I see a definite need for this!||10||17-NOV-15|
|Developer Comment: "Use a trigger". A login trigger in each database? How would that really help?||10||26-AUG-15|
|I highly agree that this should be made available in the product to allow fast, dynamic ways to apply a SQL worksheet to a schema. I have databases that have many duplicate schemas serving different customers, and it would be nice to not have to prefix all tables with hard coded schema names.||10||07-JUL-15|
|This should be a basic feature of the product.
Developers are stuck using 3.2 with extension
|I agree that adding a dropdown to select the current schema provides greater utility, and is far more intuitive, than the status quo. Unfortunately, it appears all but certain that the decision has already been made and is unlikely to be reconsidered.||10||21-JAN-15|
|Essentlal, was an extension that did this but doesn't work in new version ||10||31-DEC-14|
|I understand the developer comment says there is various workarounds, but nothing comes close to the value of having this as a drop down. I hope this will be reconsidered.||10||14-JUL-14|
|Required pls provide the same features as Schmeselect third party extension||10||12-MAY-14|
|Valuable feature that is glaringly missing||10||11-APR-14|
|Seems so simple, yet so crucial.
It's available with the "Schema Select" extension, but since v4 basically broke all the older extensions, it's no longer an option. (who knows if/when that dev will update the extension to be v4 compatible).
I consider it so necessary that I've been staying with v3.2 just so I can keep this feature.||10||17-MAR-14|
|Since the venerable SchemaSelect extension no longer works in 4.x, this would be a great addition to the application. I'm sticking with 3.x until resolved. ||9||10-MAR-14|
|Highly needed as we have databases of many schemas but personal accounts.||10||08-JAN-14|
|Would be friendly||10||24-JUN-13|
|having to issue alter session become more cumbersome, since corporate policy disconnects out session after 10 minutes of inactivity.||9||24-JUN-13|
|Would be a great enhancement!!!||10||07-MAY-13|
|Two things: First, it would be user friendly not to switch schema by means of alter session, because I'm doing it very often. Second, I would be sure which is current schema (if I work in multiple tabs, it is not so easy to handle it). So easier and transparent switching.||7||10-APR-13|
|Would be a great help.||10||03-APR-13|
|Would be really helpful.||10||20-MAR-13|
|Not essential but would be very helpful.||9||29-JAN-13|
|Nice to have. I handle it currently using folders and different connections in the Connection Tab.
However only really usefull for DBAs or Developers with DBA like powers.
But worthwhile to prevent the mess in the "Other Users" section.||8||07-JAN-13|
|Must have as default feature. However It's implemented in one of the Plugins called SchemaSelect:
|I seldom look at my own tables; they are pretty boring. I think the suggestion that someone else made of also having a default schema per connection would be a nice feature.||10||04-DEC-12|
|The Development comment that this can be achieved through snippets is not true as this does not affect the navigator which is what this feature request is all about.||10||05-JUN-12|
|Many Oracle Apps SMEs and developers focus on only a few schemas per project so this would be a great option. Thanks ||10||11-APR-12|
|Would be very nice||10||13-MAR-12|
|Navigating through the treeview past 100 'schemas' to the owner data schema view is a big usability issue for our devs. ||10||17-FEB-12|
|absolutely needed feature||10||12-DEC-11|
|This is a critical feature. I dread having to wade through "Other Users" in a large database to get to my tables/views/etc.||9||27-OCT-11|
|I have a user login and work in multiple schemata. This is exactly what I need.||10||24-OCT-11|
In our case all the objects are in another user than the one I login.||10||01-JUN-11|
|Manditory when addressing DB2 databases.||10||19-MAY-11|
|I would use it||5||11-MAY-11|
|How does having snippets make the connection tree view show the correct schema objects? I added an "alter session" snippet, but how do I apply it to the tree view's session? A must have feature! The 30 minutes to add this feature from one developer will save eons for the rest of the development community.||10||05-MAY-11|
|I have been looking for a feature like this in SQL developer. It would be nice to have it added since I am always writing that ALTER SESSION statement.
Each developer has their own username which is used to access the db. Which creates the case for this when all the objects are in a generic application schema.||10||03-MAY-11|
|This could be included with the browser schema window. Either as a setting to default the connection to the schema selected there, or as a button to set the current schema to the schema selected in the browse schema window. If the two worked together, it would make my life a lot easier.||9||08-APR-11|
|Very useful functionality||10||11-JAN-11|
|Being able to set a specific schema to use for a connection seems like a pretty standard option.||10||02-DEC-10|
|Critical feature! Um, this needs to be the top layer node in the "Connections" tree. See TOAD for details.||10||18-OCT-10|
|TOAD has this feature and it would make SQL Developer an even better alternative.||10||28-MAY-10|
|This would make SQL Developer a lot more convenient to use and more on par with Toad and other products available for Oracle. The current method of showing *ALL* the objects for the schema for the user connected to the database, and then having to expand "Other Users" to get to any other schemas, is extremely unwieldy, especially when *ALL* of the tables actually used are located in a different schema, which is commonly the case. The current method might be useful for ad hoc stuff, but not for actual databases used in production environments.||10||12-MAY-10|
|Very Good feature to have||10||07-APR-10|
|Having a dropdown to choose the current schema from is an absolute must. This is currently the only feature that prevents me from using sqldev. I usually log in to the database with a dba account and have to work in many different schemas.
All code (SQL, PL/SQL) I write has never a schema prefix, as it must run in different schemas. When opening a file with PL/SQL code (e.g. from svn), it is not currently possible to set the current schema for the compilation.
When issuing an "alter session set current_schema" command, the selected schema in the dropdown must change as well.||10||10-FEB-10|
|it should be useful||10||24-NOV-09|
|Yeap nice indeed.||10||19-NOV-09|
|I would say this feature is a must have. Would be very useful to set a default schema every time i open a connection and to be able to select schemas as we can do it on Toad. Many times i had to open multiple "Schema Browser" to compare some code. ||10||18-NOV-09|
|I need this so that I can easily change schemas to the ones that hold the application code. Security prevents me from logging into the database as the service id. As such, I must change the current schema using an alter session statement in every worksheet if I need to do anything with the service id's objects. Toad has this and I think it would be very beneficial for SQL developer.||10||06-NOV-09|
|Very useful feature.||10||04-SEP-09|
|Very nice feature to have.||10||16-JUL-09|
|Instead of choosing the schema how about using the ALL_object views, e.g. ALL_TABLES instead of USER_TABLES.
A filter can be applied to see the only one schema if wanted.
Explanation. I have users that only have access to a READ_ONLY user (only select rights on tables in many different schemas). They see no tables in this schema and complain that this is possible in MS Access.
|I stumbled upon this feature request while looking for a way to make it easier to look at tables in other schemas. This has been a real pain in using SQL Developer, especially with hundreds of developers, trying to navigate to the application specific schema.||10||28-MAY-09|
|It looks like there are two or three different requests here. 1. Add dropdown to sql worksheet to change schema. 2. Add schema to connection dialog and show tables etc at root instead of Other Users. 3. Add filter to connection node and/or Other Users that allows user to specify schema(s)
My scenario is that we're given a personnel logon and are typically working with a specific application and must always navigate to Other Users. I vote for number 2.||7||09-APR-09|
|My need is for the Object Navigator is use the current DEFAULT_SCHEMA. Or to be able to open an new Object Navigator window that does. I'd prefer to be able to set and change DEFAULT_SCHEMA in session either in an SQL worksheet window or as a right click option in Object Navigator. But setting it at the connection would work.||9||11-MAR-09|
|Very useful feature!||9||28-FEB-09|
|I'd really like to have an additional drop down to select the current schema.||10||04-FEB-09|
|I agree that this is important. I use one schema the whole time but it's not my default schema and I cannot change my permissions.||10||22-JAN-09|
|It is the one issue that prevents dept wide use at my site. Being able to specify a default schema on the connection details would be the icing on the cake.||8||03-DEC-08|
|toad, golden and others have a dropdown box listing the schemas. This makes it easy. This can be saved with the SQL Developer connection info so that you don't have to do this every time.
I tried to do alter session set current_schema, but this does not affect what is show is the tables list. This is not adequate.
I don't see what snippets has to do with this.||10||05-NOV-08|
|Would be great to get this available on the connection definition window, but really want current schema to affect the details displayed in the connection navigator as the current schema's objects||9||04-NOV-08|
|This i a very important feature for database with tons of schemes/users. Although there is a workaround using snippets, it would be alot more user friendly to just add this option when creating a new connection.||10||29-OCT-08|
|Would like to see this addition. It would come in very handy for us Peoplesoft users who must connect as own user, but spend all there time in sysadm schema.||10||15-OCT-08|
|Yes please. This would be much easier than going through other users.||8||01-OCT-08|
|Add an ability to define a filter on schemas, so that only the schemas you are interested in show up in the lists/navigators.
|on some of our servers we have hundreds of schema's so having to scroll down all the time is a real pain.
|This feature could be the one thing that will make my customers choose TOAD over SQL Developer. Each user must have an Oracle ID, but all access data on one production schema. (Users schema are always empty!)||10||07-AUG-08|
|Yes, it would be a nice feature to have.||10||30-JUL-08|
|It would be very nice to be able to "See" these schema_owner's objects in the navigation tree when using the alter session set current_schema = ... syntax!||9||28-JUL-08|
|Setting a default schema as part of the connection properties is an excellent idea.||10||05-JUL-08|
|Just add a text box in the connection creation window to enter a default schema. This gives you the option of connecting to a different schema than the one related to your personal user account. This way if you connect as user ABC you can still connect directly to a default schema of XYZ. At our organization of hundreds of developers and users we login user our personal user account but do all our work in an application specific schema. When creating a connection definition in SQL Developer we would include the database, our user account/login information and the default schema would be the one for the application we are developing or maintaining. This default schema would be the one who's information is displayed in the primary tables, views, packages, etc. at the root of the connection tree display (rather than having to select a schema from the hundreds of entries in the "other users" folder).||10||24-MAY-08|
|Would be nice to have this TOAD like feature, for the schema selections. It oftes takes lonjg time to switch when you have multiple accounts.||7||08-APR-08|
|You may need some additional privileges but you could use an after logon trigger to set current_schema as another schema by default.
using ALTER SESSION SET current_schema=otherschema
|When a default schema is specified or the schema is changed update the object browser so you don't have to go to the 'other users' section to view the objects.||10||07-DEC-07|
|Yes, I think this will be extremely useful.||10||30-OCT-07|
|I would definitely like to see this feature. In virtually every Oracle db I work, I must change the default schema. I've created snippets, but it's a bit cumbersome. I'd love to see both a "Default Schema" option for a connection as well as a schema drop down.||10||10-OCT-07|
|This would be very helpful.||10||08-OCT-07|
|Working with database where many schema are available are really pain in the neck; accessing them throw "other users" are possible solution but far from being elegant, neither being quite useful.||10||09-AUG-07|
|This would be a great feature to add. I have been trying to import from Excel and when SQL Developer creates the insert statements, it doesn't append the schema name to the table so the import fails. It only works if you are logged on as the owner of the table.||10||19-JUL-07|
|Yes, you can work around this but it would be a useful addition.||7||13-JUL-07|
|I would like to see a default schema implemented as part of the connection properties. That would give access to the objects in the object navigator and allow schema switching by the connection chooser drop down in the upper right corner of the SQL worksheets.||10||02-JUL-07|
|The is the reason I don't use SQL developer. Our DB's have 100's of schemas, I log in as one user, and *never* work with that particular schema. It's too annoying to deal with the "other users" node for 100% of my work.
This is really screaming for a "default schema" in the connection options as well.||10||29-JUN-07|
|It would be desirable for SQL Developer to at least track the current schema. For example, if you change the current schema and then use EXPLAIN, SQL Developer tries to display the wrong schema's PLAN_TABLE.||10||19-JUN-07|
|Changing schema in the SQL worksheet doesn't get me into the schema in the object navigator. It would be very helpful to have the ability to set the default schema for both the worksheet and the object navigator, rather than having to separately navigate inside the Other Users box and alter the worksheet session.||10||25-MAY-07|
|I would like to actively move between schemas easily. Not easily done now.||10||17-NOV-06|
|Yeah, I don't like having Other Users. I want to see all objects from all users with objects. Or all non system objects from all non system users with objects.||6||02-NOV-06|