Skip to main content

OOW2010 Wednesday

Alas I missed the Benelux cocktail part last night, because the dinner took somewhat longer than expected. The dinner was extremely good though.
This day started with a session by John Scott Spendolini about "Recovering from APEX mistakes" - I didn't know they existed but nevertheless. Good session on how to undo changes you've made, debugging etc. The next one was by Marco Gralike on XML-DB (what else could it be?). Good, detailed info with some nice examples. Not all demos worked like he meant to, but that's the price you pay when you mess with them the night before! Especially the event firing mechanism when you drop a file in an XML folder are very cool! Marco, we definitely need those for our ODTUG presentation!
Then Raj did a presentation on collections, enthusiastic and dynamic us usual. But also his deno didn't turn out as expected. The best take away from this session was the idea to create views on top of your collections, so you can maintain the code more easy.
Larry's Wednesday's keynote was rather disappointing. No new announcements, just a recap of the things announced earlier this week. And that took rather long, so I missed the Fusion Apps demo as I headed for a session on EBR by Boeing. They already really use it in their mission critical business applications. By implementing EBR they managed to reduce the outage for an application upgrade from 9 hours to less then 1! Very impressive.
Next was the Blogger Meetup. Always a good opportunity to match faces with names. And the. Off to the Appreciation event! It was definitely more crowded than last year, with long lines for the food. And some good bands too! Don Henley may look somewhat older, but his voice still sounds like 30 years ago. And the Black Eyed Peas surprised me, with a very good show. This is the first time I saw the whole crowded joining the band: All yo part people in da house, say yoo-hoo.
I got a bus back around 12, because I need a relative good night sleep for my session tomorrow. I am curious how many people will show up, as I heard a lot of people saying they'll leave on Thursday....

Comments

Popular posts from this blog

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

APEX ReadOnly Pages - The easy way

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