This content has been marked as final. Show 5 replies
thanks for your reply and the detailed blog article.
Actually I was not aware of this functionality and it may probably help me.
The only issue I see with the History window is that the information it stores can be accessed only from inside SQL Developer, while in the case of a simple backup file I can quickly view and diff it against the main file without the need to open SQL Developer (that notoriously is not lightning fast when loading).
I agree that this new approach could be an issue only for a few developers (depending on their personal habits and preferences), but I still believe that having backup files should be at least an option.
Anyway I will try to use the History window and see if it fits in my workflow.
If you want faster load times, try disabling the Migrations extensions in the preferences. I was able to go from 30 second load time to about 10 second load time
If you want to save copies of your changed files and have them available outside of SQL Developer, have you given consideration to a full source control system? Even if it's just for you there are many advantages to this. And SQL Developer can even build one for you - a local Subversion system.
thanks again for your reply.
I already disabled what I don't use, but the load times are still far slower than a native windows application like PL/SQL Developer, so that won't help.
Finally, I already use a full blown VCS (SVN 1.7), but as I already pointed out in my initial post (please read at least point 1 and 2), you cannot use the VCS as a dumpster. Moreover the version of SVN we use is not supported by SQL Developer, so working copies MUST be handled OUTSIDE the closed environment of SQL Developer.
Anyway this is just one among several reasons why I finally dumped SQL Developer and returned to use the trusty old PL/SQL Developer that is way faster in every respect (even for just searching for database objects). After using SQLDev exclusively for several months, I finally realized that I don't want a slow death by a thousand cuts.
I reserve myself to test it again when/if version 4 comes out.
Thanks for the help,