Skip to main content

My OOW 2013 Expectations

Redwood Shores, Thursday September 19. 5:30 AM. 
5:30 AM? So I must be in the "wrong" timezone.... Just like most European based Oracle ACE Directors in this hotel I woke up early. Not as early as some others - I noticed tweets from around 2:30 - but nevertheless early.
After a decent flight with some sleep and a few movies we arrived at San Francisco airport yesterday around noon. We were already warned by the flight attendant about the long lines for immigration, but this wasn't quite what we expected:
Usually the line starts somewhere in the big hall but this was about 200 metres before the hall! So expectations were set at a 3 hour waiting time ... After one hour we arrived in the hall and then it showed that half of the hall wasn't used for the queues - which is a good thing, because then there are less people in front of you as you night expected - but also half of the booths weren't used. And that was what caused the long delay in the first place. Probably due to the government expense cut (a.k.a. sequestration). So all in all it took about 1.5 hours. One advantage : You don't have to wait for luggage - that's waiting for you!

Today is the first day of the ACE Director briefing. In these two days the announcements done at Open World will be revealed to us and discussed with the Oracle Product Managers / Directors and such. Also Thomas Kurian will stop by to tell us where Oracle will be heading and to answer the question from the audience (I guess it'll be around 75 people).
When the show starts we will be under NDA, so we can't tell / blog / tweet anything about until Larry or another Oracle presenter has officially announced it.

So right now I can only guess... I expect some of the Exadata features will be available for "regular" databases as well. So more compression options for instance. I expect more "in memory" database features will be announced as well as more Big Data / NoSQL stuff. Maybe even an appliance? Like a Oracle Big Data Appliance (OBDA)? With all the Hadoop, MapReduce, NoSQL and database stuff in one piece? "Engineered to work together"? We will see ....
Last year the motto was : Cloud, Mobile. Social.
Cloud... Oracle did release the Oracle Cloud early this year and will extend their offerings. Mobile ... We did get more mobile Fusion Apps, ADF Mobile and APEX Mobile, So that's covered as well. Social...  Oracle did announce the Oracle Social Network last year. Never heard anything from that since! Did you?


Comments

Popular posts from this blog

Filtering in the APEX Interactive Grid

Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good o...

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

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