Skip to main content

Oracle Designer Extension for SQL Developer

Image
By
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

Labels:

Comments

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

Popular posts from this blog

Filtering in the APEX Interactive Grid

By
Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good o...
1 comment
Read more

Stop using validations for checking constraints !

By
 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function ...
Post a Comment
Read more

Refresh selected row(s) in an Interactive Grid

By
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...
Post a Comment
Read more