Skip to main content

Oracle Designer Extension for SQL Developer

In SQL Developer there is an Application Express node. That is a great way to browse through the APEX Repository. And wouldn't it be great if you can use the same technique to browse your Designer repository?
Can we build it...yes we can...
Using User Defined Extensions you can create something like this:'Just' create an XML file to query the Repository and add it as an extension of the Navigator type. This XML file does what is shown in the pic above (it is not finished yet, and anyone who wants to contribute...feel free to add more subnodes/details!). Just click on 'expand source' to see the code.















SELECT 'Entities' name from dual
union
SELECT 'Functions' from dual






















SELECT b.id, b.name
from ci_app_sys_entities a
, ci_entities b
where a.application_system_reference = :APP_ID
and b.id = a.entity_reference
and 'Entities' = :SEL_NAME

























SELECT a.id, a.name
from ci_attributes a
where a.entity_reference = :ENT_ID



























SELECT b.id, b.short_definition
from ci_app_sys_functions a
, ci_functions b
where a.application_system_reference = :APP_ID
and b.id = a.function_reference
and 'Functions' = :SEL_NAME























Comments

amihay gonen said…
I can't see the xml , i think it is some problem with the blog , can you check it ?
Roel said…
It should be better now - just click on 'Expand source'.

Popular posts from this blog

Fix Interactive Report headers issue when using a Region Display Selector

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.

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

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...

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 wors...