Skip to main content

ODTUG: Monday

The day started with the General Session. There the ODTUG Board announced when en where the next Kaleidoscope will be held: At Long Beach, California! From June 26 to 30 2011. And you can even submit papers as from now! There is a link somewhere, and if I'll find it I'll add it to this post. Another remarkable thing was that the number of attendees this year was up with 50% to around 900! So ODTUG grows bigger and bigger every year - and so even getting more important in the Oracle world.
Next - and rather important - was the game...The Netherlands against Slovakia. We saw the match with a couple of other attendees, most of them Dutch, but also some other guys - but all supporting Holland And we won with 2-1, which was great. So in the next match we have to beat Brazil - which will be though!
Back to the stuff we all here for...
The first afternoon session was the "APEX 4.0 Keynote", where Mike showed all the cool new APEX 4.0 features for an interested audience of over 250 people (rough count). Nice to notice that even my name was mentioned when Joel answered a question about upgrading to 4.0: "If your name is not Roel and do not live in The Netherlands, you'll be fine". ..pointing out to a bug a discovered only 15 minutes after 4.0 was released - BTW that bug has been fixed the same day!
For the next hour I was the ambassador for Anjo Kolk's session on "Accessing databases from Google Apps" Completely off the APEX topic, but nevertheless very interesting.There seems to be an App store like marketplace for Google apps - really didn't know that. Anjo showed how to extend a Google spreadsheet by accessing data from a mySQL server using jdbc. An Oracle extension is in the making. You can also get data from your database using import functions.These functions are insecure, but if you want a secure connection - and are willing to pay for it - you can use the Secure Data Connector. That SDC uses tunnelling via the Google Tunnel Servers.He also showed how to query (and update) data in a Google database with the Google feedserver. Getting this working is not that easy, requires some tweaking and modifying XML files, but the result is nice. You can also use PL/SQL functions that return JSON to feed Google Visualizations and show these graphs in iGoogle - and so you create your own dashboards on the web, using real live data from your database!
In the next session, called "APEX; A window to the Oracle Database", Anton Nielsen demoed how to use some cool advanced database features in APEX. Like Oracle Text (with "smart searching"), Analytic functions, Intermedia for images (thumbnail generation, rotation, capturing metadata etc) , external tables and VPD. The key of all this is, if you can do it in the database you can do it in APEX as well!
During the Sundown Sessions - a sort of Q&A session - a lot of good questions where asked and answered. The main announcement was that the APEX Listener was released just that afternoon!
After the reception (more food and drinks), there was a poker game organized in the bar. I joined the hard core players, and managed to end as third (and it actually was my first real poker game ever!), So in the end I got my 20 bucks entrance fee back! It was a lot of fun - and we stayed up until .. let me say ... late.

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

Stop using validations for checking constraints !

 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function ...