Skip to main content

ODTUG: Thursday and the day after...

By
The last day of this great conference had "only" three presentation slots. The first one I attended, but honestly I didn't pay that much of an attention. I was writing my previous post at that time and I was rather familiar with the subject "Forms to APEX conversion". And I totally agree with the conclusions: Converting simple Forms is easy, but the more complex the Forms, the more work it will take to convert it to APEX!
The second one was called "APEX Stimulus Package". In fact it was more or less a list of things you have to consider to improve the performance of your APEX application - also due to the fact that most demo's didn't work because of a failing internet connection. 
To name some of the tips: Reduce images sizes and use png instead of gif or jpg; check the Apache log for errors and resolve them; add a favicon.ico; watch out with pagination schemes; tune your Page 0 processes; use Page and Region caching where appropriate; minify javascipt and css files; externalize javascript and css files; refactor PL/SQL etc. Some of the tips where obvious, some of them quite useful.
The last one of this week was rather cool. Roy McLean showed how to use Oracle Data Mining in combination with APEX. I never used the Data Mining stuff before, and you might need a degree in maths to use it properly, but the things you can do are rather amazing. For instance you can predict what probably will happen. As an example Roy showed a sort of Helpdesk application where a call was assigned to a certain (pool of) engineers by the text that you entered when describing the problem!
After the show was over I paid a visit to Obama's house, the Washington Monument and checked out the West side of The Mall.
The day after. Friday, I had until 10PM before my flight was leaving, so I visited the Capitol and "did" the East side of The Mall. The weather was fine (cooler than at home!) and it was good fun.
As in previous years I liked ODTUG very much - the best conference in the world. Hope to be there again next year in Long Beach, California.
Labels:
Location: Woodley Park, DC, USA

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