Today is the day! We have new releases of both SQL Developer and SQL Developer Data Modeler.
I’ve been talking about v4.2 tweaks and enhancements for awhile now, and here’s the full list if you want to go back and review.
I’d like to share a few highlights though.
But first, FULL STOP. Go click that big button to the top and left.
Ok, let’s continue.
I’d like to thanks the entire community for all the feedback, especially those of you who provided test code to exercise the new formatter. We made a few changes since the Early Adopter 2 update – tons of bug fixes, and tweaked the options a bit more based on your feedback.
With 4.2 now live in production, if our parser (and accordingly our formatter) doesn’t understand your code, we just won’t format it. In the EA’s we printed comments that showed the code bits we didn’t understand. For v4.2 production you should just see the parser ‘squiggle’ indicating where the code isn’t being interpreted correctly. Please share your code samples with MOS and the community if you think that’s a bug.
Some things of note:
- The preferences have moved AND changed from version 4.1. They’re now under the Code Editor page, and should also be simpler to understand now.
- There’s a ‘simple’ mode, and advanced mode, and an uber-expert mode.
- In advanced mode, you can format your code by hand, paste it into the preferences, and we’ll auto-detect how you want your code to look going forward.
- In uber-expert mode, you can tell the formatter exactly what to do to your code. Our developer Vadim has a couple of blog posts showing how to do this with examples.
Not a new feature – we first introduced the Instance Viewer in version 4.1. But we now offer a ‘Top SQL’ report. See your expensive queries, and drill down into them to see what’s going on or fix them.
The licensing prompts on the drill down report let’s you know that the SQL Tuning Advisor and Run time history reports require the tuning and diagnostic packs, respectively. If you don’t click on those reports, then there’s nothing to worry about.
Everything the Instance Viewer hits on the main panel is of the ‘no additional cost’ data dictionary views category.
Easy Peasy Password Resets
No more requiring an Oracle Client to change your database passwords when you’re not already connected. Maybe the most compelling reason to upgrade your end users.
More details here.
12c Release Two Enhancements
We support big-ole object names now.
And you can create Analytic Views too!
And the Multitenant option got a lot of upgrades. Among them, Application Containers. We support those too.
New to 12cR2? Did you know our VirtualBox VM was upgraded to 12.2? Also has APEX 5.1 and ORDS 309 for ya.
Speaking of ORDS…
You can now manage your RESTful Services directly in the database connection tree! This is much easier than setting up your ORDS Dev user connection. You’ll see the new REST item in the tree, and I talk about this here.
And the Modeler!
I think the biggest two changes of note are the ability to include your diagrams in your HTML and PDF reports AND the ability to now store your repository in GIT.
On the diagrams, you can ask to include them in your reports AND you can just directly print them to HTML/SVG.
And we get..
Et cetera and potpourii
This marks the end of the SQL Developer version 4.X releases. We’re moving towards a quarterly release schedule to synchronize up with our Database Cloud Services updates. So our next version will start with a 17 – for 2017, then quarter (1,2,3,4), then week.
This release also ships with the fewest known number of bugs…ever…for a SQL Developer release. We hate bugs. So we tried to kill ’em all. I’m sure you’ll find some more. Let us know. We’ll be able to release updates more frequently, getting you bug fixes that much faster.