Posts tagged sql developer
Currently at Tom Kyte’s session regarding topics new, improved or coming in Oracle Application Development. Tom told about the history APEX has gone thru and the current setup with the APEX Listener and even the “PL/SQL Gateway” was mentioned. I always have to laugh a bit because this last one touches the XDB Protocol Server which can do way more then only this PL/SQL extension for APEX which has been embedded in this XDB Protocol Server framework. There is a APEX book out there that touches a bit the possibilities of the framework, one of the reasons I will promote and explain it a bit more during conferences like UKOUG, because I think its a shame that people don’t know its full potential. Anyway. Tom stressed once again that APEX is a serious environment regarding the huge websites out there based on APEX supporting 1000th of user sessions. Also it nowadays had a better debug support (4.1) and use / support for ROWID, improved data upload and calendar wizard support and redesigned websheets in APEX 4.1.
One thing that always draws me in tools, libraries and frameworks: what are the hooks, the backdoors, the extension points, the APIs, the event listener registration facilities etc. Today I came across a blog article by Roel Hartman, about showing Oracle Designer objects in the SQL Developer database navigator. I could not resist looking into the extension mechanism used for this. And of course the best way to understand this, is by doing it yourself. So in this article my brief description of how to extend the Database Navigator in JDeveloper (which is the same thing as in stand alone SQL Developer).
My extension is primitive and pointless in the extreme. It has the navigator show a new node type called Employees. The child nodes are the employees specified in table EMP. The interesting part of course is that you can any information found in the database – either the data dictionary or your own tables and views. This allows you to integrate Business Rules if they are defined in tables. Or Tasks, Issues, Projects and Team Members – if they are in tables. Or the results of calling WebServices – if these results are exposed through Views.
After Web 2.0, Enterprise 2.0 and Wife 2.0, Oracle introduces the term DBA 2.0. It seems to refer to the DBA of the very near future. The one who can rely on a formidable pal hiding inside the database and taking on many of the boring, repeating tasks as well as advising on some of the tougher challenges when it comes to managing the database. Manageability is one of the focus areas for Oracle in the marketing strategy for the database as well as in the development budget allocation. Lots of time and energy are invested in making the database more manageable and striking the optimal balance between automated management and human decision making.
DBA 2.0 is perhaps also the guy about whom Mark Townsend,Vice President Product Management for Server Technologies, said: "to really screw a system up, you have to be a DBA!". To which he added: (more…)