Skip to main content

Extending SQL Developer with Designer data

Image
By
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!
Labels:

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?
4:15 am
John Flack 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.
7:49 pm
Post a Comment

Popular posts from this blog

Fix Interactive Report headers issue when using a Region Display Selector

By
When you have multiple Interactive Reports (IR) on your page and use a Region Display Selector to mimic tabs, you might notice some weird behaviour in the IR headings if you switch tabs. The headings are not positioned correctly and you get an extra empty row under the headings. It just looks weird and ugly. But if you resize your browser window, it all looks fine again (until you switch to another tab..) So can we fix this by creating a Dynamic Action that mimics that "browser window resize" event? Yes we can! Create a Dynamic Action that fires on Click of the jQuery selector li.apex-rds-item a . That should fire a JavaScript snippet :  apex.event.trigger(this.triggeringElement, "apexwindowresized"); So now a click on a tab not only switches from one IR to another but also fires that event that will "autofix" the IR headers. A simple solution for an annoying problem. This applies to APEX 5.0, I assume it will be solved in 5.1.
Post a Comment
Read more

How to create neatly formatted Excel documents using PL/SQL?

By
If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...
21 comments
Read more

APEX ReadOnly Pages - The easy way

By
If your Oracle APEX Application requires different types of access - full access or readonly - for different types of users, you can specify a Read Only Condition on Page level (or Region, Item, Button, etc.).  You can set an Authorization Scheme on Application level, so it'll be applied to all pages. So if you have an Authorization Scheme named 'User Can Access Page' defined by a PL/SQL function like this: return apex_authorization.user_can_access_page ( p_app_id  => :APP_ID , p_page_id => :APP_PAGE_ID , p_user    => :APP_USER );  then you can code all the logic in the database using the APEX Repository, your own tables or a combination to define whether a user has access to that page or not. But alas it is not possible to define something similar Application wide for a Read Only condition. You can specify an Authorization Scheme 'User has Read Only Access' using a similar signature as the one above and use that on each and e...
Post a Comment
Read more