Skip to Main Content
Forums

SQL Developer

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Is there some way to save current layout in SQL Dev?

Blue BirdSep 18 2019 — edited Sep 18 2019

I would like to know if exist some way so I can retain visual layout of my open tables and unsaved worksheets with code inside if I close and reopen SQL Developer?

For example I have open 3 tables with Data or Columns tab open and couple of Worksheets with SQL code inside but it's not saved yet. When I for example restart SQL Dev all are gone. For example in Notepad++ all unsaved windows reopen when you restart application.

I know that saved worksheets reopen but many times you just have some scratch papers with code and tables for temp use. How do you recreate your layout (tables, worksheets) if you have to close SQL Dev because of some other external reason, e.g. restarting PC?

Regards,

BB

Comments

Gianni Ceresa

Hi,

I'm not really sure to understand what your question is about as you talk about dimension first and then about a prompt on a column ....

If you have a "Year" column which is used in a prompt and instead of YYYY you want to display YY-YY (so 2017 => 20-17 etc.) then it will be a string, and you can simple cast the year as string and then use substring to split the first 2 characters , concatenate the '-' and add the last 2 characters.

But it will not be "Year" anymore, it will be the formula you wrote as string. So all depends what you want to do with it.

1 person found this helpful
Martin van Donselaar

Not exactly sure what you mean but if you generally want years to display as YY-YY then the best way to do this is to add a column containing this value to your time dimension.

user11440683

Beware of putting function logic on time measures that you then use as filters.

This will have a very real impact on performance.

Better is either to have the values populated in the format that you want in the data warehouse, or if that is not possible then tell the end user population to live with it, the trade off on speed is not worth the cosmetic appearance!

3 people found this helpful
3427784

Thank you all, we were able to efficiently convince our customers this unnecessary cosmetic change will lower performance and was able to keep it in the same format as a year should!

3 people found this helpful
Christian Berg-0racle

WTH just happened? A customer listened to community advice? Lollipops for everyone!

3 people found this helpful
3427784

LOL, I was thinking the same. A bold move but worked out due to the technical advice provided on this thread regarding unnecessary changes! Cheers to all !

1 person found this helpful
1 - 6

Post Details

Added on Sep 18 2019
#sql-developer
2 comments
1,510 views