It’s that time of year again. After last year’s OTN Appreciation Day this year there is another ODC Appreciation Day (“since Oracle Technology Network (OTN) has now been renamed to Oracle Developer Community (ODC) there is a name change for the event this year, but the idea is the same.”) powered by Tim Hall.
Last year I decided to vote for the Dual Table. This year I would like to give my shout out to the Oracle BI Server. The reason why I like this server so much, I explain here.
Thanks to Tim for organising this event. Looking forward to all the different contributions. Curious what other people have to share on ODC Appreciation Day, check here.
I have been working with Oracle products for about 20 years now. One of the great things about Oracle is the Oracle Community. Central platform within this community is the Oracle Technology Network (OTN). I have been frequenting OTN loads of times (downloading software, exchanging knowledge on the forums, etc. ). A lot of people I know in the Oracle Community, I have met via OTN.
Today I read the OTN Appreciation Day announcement on Tim Hall’s blog.
“considering OTN is all about community, I figured it would be fun if we got as many people as possible to write a small blog post about their favourite Oracle feature and we all post them on the same day”
I immediately thought about the Dual Table in the Oracle database.
What I like about the Dual Table, is that something which looks so simple can be so powerful. You can select the date, the length of a string, the result of calculation and so on. One simple table, with just one varchar dummy column is able to tell you almost everything you want.
I can illustrate how powerful the Dual Table is by a short anekdote. The story could be a little bit different but it’s all about the scope. One of my former colleagues (I won’t tell his name) wanted to test part of his code. Therefore he decided to insert a record in the Dual Table. I think it was in the Oracle database version 7 / 8 timeframe. It might have been a smart move in his mind, but it was disastrous for the application running. Very slowly the application collapsed. The application code expected one row when selecting from the Dual Table. It took some time to realise that the Dual Table contained an extra record. As far as I know the functionality of the Dual Table has changed since then, but I guess there is no need at all to mess with the Dual Table.
Curious what other people have to share on OTN Appreciation Day, check here.