Skip to main content

OOW 2009 : Tuesday

By
This day started easy by skipping the keynotes. So the first session I attended was at 11:30, called The Life of a Query in which the presenter revealed the details on the internal processing of the Oracle database.
Next was Giving your Application Express a Web 2.0 Facelift. Not that many new things, but Raj is always very entertaining to watch. The most interesting thing I saw was a new prototype of the APEX Developer page on Patrick Wolfs laptop: Instead of the current Page Definition view (with Page, Regions, Items, Processes and so on), the same information was presented in an DHTMLX tree view! Patrick showed how you can easily re-order Items, copy buttons etc by just dragging them around in the tree. And on every object you can do a right mouse click that would present the actions you can do with that object. It looked very slick! We shortly discussed whether or not you should expand that tree with one level (Page) or even two (Application), to make it even easier to copy and move Pages or Regions around. Imagine something like the tree view of your application in Oracle Designer - but then better looking. I guess this prototype won't make it to APEX 4.0, but it shows that the product is still evolving - even after APEX 4.0!
After that Understanding Real Application Clusters for Developers was on the program - I guess using Dummies instead of Developers was to offensive. However it was a reasonable good overview about RAC, but didn't associate about anything that a developer might have to do with it. And the presenter ran seriously out of time....
The last one of the day: Oracle Performance by Design. A presentation full of half truths and generalizations. So no further comments....
In thee evening there were three meet-ups to attend: The Blogger MeetUp, Benelux Cocktail Party and the APEX MeetUp. I had to pick and did the first and the last. Alex G., who organized the Blogger thing this year, also introduced a nice competition. He/she with the most names on their new T-shirt (with the text "I met more bloggers than you"), would win a netbook! So there was a lot of signing going on! Good job, thank you Alex!
And of course, at the APEX meetup al the usual suspects where there. And - as every time - it was really nice to meat each other again!
Labels:

Comments

Post a Comment

Popular posts from this blog

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

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

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