Skip to main content

ODTUG Kaleidoscope 2008 : The day before


After an 18 hour trip from my home I arrived at the Sheraton in New Orleans. Luckily this time I also got my bag (at OOW 2007 it arrived a day later). A small wonder, because my transfer time in Houston was reduced from 1 ½ hour to 20 minutes due to the border control officer, who seemed to be very interested in all my predecessors in the queue. So I had to run from gate E to C. On the way I saw at a screen that The Netherlands where ahead against France with 1-0. At the time I arrived in New Orleans I called home and found out it turned out be a 4-1 victory!

When I came outside of the airport the tropical atmosphere hit me. It was about 32 C, but very very humid. After dropping of my luggage and freshening up a little in my room at the 43 floor, overlooking the Mississippi, I went out into the French Quarter. This area is packed with bars and restaurant and every bar seemed to have it’s own live music. I managed to stay awake until 9pm - that makes about 22 hours awake - and slept until 6:30 the next morning.

When I stepped out for a nice and quiet stroll through the French Quarter and the riverside it was so hot and humid already - or still - that my sunglasses blurred immediately. Like stepping into a tropical swimming pool. After my walk I took the old steamboat for a trip over the Mississippi and strolled over the Cajun / Zydeco and Tomato festival. New Orleans is very very lively: there is music on every corner and food stalls in between them. And of course the obvious street artists painting, breakdancing and reading hands. In this part of town there is not much damage left from Katrina three years ago, but also it didn’t suffer that much from The Storm as the locals seem to call it.

I hope I am over my jetlag already and ready for the start of the conference tomorrow morning at 8:30 : a full day ‘APEX Must hear success stories’

For those who are more of the visual type, I uploaded some pictures here.

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