Skip to main content

OOW 2008 - Summary

After being on the road for 8 days, I am finally almost home - at my parents in Connecticut for a weekend visit.

OOW was in a word, hectic.  I was afraid that it would actually be a bit worse, as it's hard to fit 43,000 people into a city and not have a suite of the obvious logistical issues.  Oracle did a fairly decent job, given the fixed issues of the sheer size of the conference.  Most of the presentations that I wanted to see were in Moscone West or the Marriott, which were just across from one another, which did make things easier.

The registration system was a little bit less than I expected.  I would have liked to have had an interface that would let me know which presentations were coming up next and/or have an easy search to show me not only that but which presentations were in a specific venue.  Often, I found myself walking out of a meeting and would have liked to sit in on something close, but had no way of knowing aside from walking the halls and hoping to stumble upon something interesting.  Pre-registering was a nice idea, but I did change my mind on a number of things.  It would also have been nice to not have gotten evaluation e-mails for presentations that I did not attend. 

As for the big announcement, ehh...  I guess that I'm tainted by the excitement that companies like Apple create with their announcements, as I can go out and buy (or at least afford) most of the products that are announced.  With the "Database Machine", I just can't see sleeping outside of Redwood Shores so that I could be the first one to have one.  It is an intersting announcement, as Oracle has done this in the past with limited to no success.  Perhaps the second time is a charm...

Comments

Popular posts from this blog

Custom Export to CSV

It's been a while since I've updated my blog. I've been quite busy lately, and just have not had the time that I used to. We're expecting our 1st child in just a few short weeks now, so most of my free time has been spent learning Lamaze breathing, making the weekly run to Babies R Us, and relocating my office from the larger room upstairs to the smaller one downstairs - which I do happen to like MUCH more than I had anticipated. I have everything I need within a short walk - a bathroom, beer fridge, and 52" HD TV. I only need to go upstairs to eat and sleep now, but alas, this will all change soon... Recently, I was asked if you could change the way Export to CSV in ApEx works. The short answer is, of course, no. But it's not too difficult to "roll your own" CSV export procedure. Why would you want to do this? Well, the customer's requirement was to manipulate some data when the Export link was clicked, and then export it to CSV in a forma

Refreshing PL/SQL Regions in APEX

If you've been using APEX long enough, you've probably used a PL/SQL Region to render some sort of HTML that the APEX built-in components simply can't handle. Perhaps a complex chart or region that has a lot of custom content and/or layout. While best practices may be to use an APEX component, or if not, build a plugin, we all know that sometimes reality doesn't give us that kind of time or flexibility. While the PL/SQL Region is quite powerful, it still lacks a key feature: the ability to be refreshed by a Dynamic Action. This is true even in APEX 5. Fortunately, there's a simple workaround that only requires a small change to your code: change your procedure to a function and call it from a Classic Report region. In changing your procedure to a function, you'll likely only need to make one type of change: converting and htp.prn calls to instead populate and return a variable at the end of the function. Most, if not all of the rest of the code can rem

Logging APEX Report Downloads

A customer recently asked how APEX could track who clicked “download” from an Interactive Grid.  After some quick searching of the logs, I realized that APEX simply does not record this type of activity, aside from a simple page view type of “AJAX” entry.  This was not specific enough, and of course, led to the next question - can we prevent users from downloading data from a grid entirely? I knew that any Javascript-based solution would fall short of their security requirements, since it is trivial to reconstruct the URL pattern required to initiate a download, even if the Javascript had removed the option from the menu.  Thus, I had to consider a PL/SQL-based approach - one that could not be bypassed by a malicious end user. To solve this problem, I turned to APEX’s Initialization PL/SQL Code parameter.  Any PL/SQL code entered in this region will be executed before any other APEX-related process.  Thus, it is literally the first place that a developer can interact with an APEX p