Skip to main content

Extending SQL Developer with Designer data

Using the Preferences of SQL Developer you can register a User Defined Extension (UDE). This UDE is just a small XML file containing a command or query. If your Oracle Designer Repository is queriable by the user you use for your connection, you can show the Table Definitions in Designer alongside the definitions in the Oracle Database. You just have to create an XML file containing this code:

Register the file as an 'EDITOR' type in SQL Developer using Tools / Preferences / Database / User Defined Extensions. Restart SQLDev and the result is something like:

Is it usefull? Not really with this query, but you can extend the query with a lot of other data, for example to list the modules a table is used in or the column definitions of that table!

Comments

Stew said…
Roel,

Since you're a SQL Developer hotshot, do you have any idea what the queries are that it uses to display the Apex data? Is it simply querying against the appropriate Apex Views?
JCFlack said…
I saw Sue Harper demonstrate this feature of SQL Developer at ODTUG and I was pretty excited about it. I too want to add some selects from the Designer Repository. But I'd like to add a whole tree of Designer stuff to the navigator. Looking over the documentation, it isn't really clear to me how to do it. Your example and others like it give me some ideas about how to do it, but without good docs it is hard to make the leap from the example to what I want.

Popular posts from this blog

apex_application.g_f0x array processing in Oracle 12

If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one:
then you disable the "Escape special characters" property and the result is an updatable multirecord form.
That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for processing y…

Adding items to your Interactive Grid Toolbar

The APEX Interactive Grid uses the Toolbar widget to create the default Toolbar showing the Search box, Actions menu, Save button etc. And since quite a while there is a nice Plugin "Extend IG Toolbar" by Marko Goricki that makes it very easy to add additional buttons to the Toolbar.

But what if you need more than a button? 
Inspecting the contents of widget.toolbar.js, you can easily spot there can be added more to the Toolbar than just a button: The type of control, available values:
"STATIC", "TEXT", "SELECT", "BUTTON", "MENU", "RADIO_GROUP", "TOGGLE".
The first example will show a way to easily switch from one filter to another. Of course we could use the standard functionality and create two different Report views, but using a Radio Group on the Toolbar gives a more "Tab" like user experience.

So how can we create a Radio Group that looks like a switch in the Toolbar?
In the Javascript Code …

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid. The use case I'll cover right here is probably more common - and therefore more useful!

Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user.The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even worse) while you…