Skip to main content

Chatting with the database

By
At APEXPosed in Brussels I attended a presentation by Lucas Jellema called "Reaching out from PL/SQL". It was all about leveraging the central position of the Oracle database in the application architecture. Of course the examples were accompanied by some fine demo's. One of them was sending and receiving email by the database: You could ask the database a question, and the database answered that one. Another one was sending instant messages from the database when some data was changed. Interesting stuff!
So I decided to combine those two: Why not chat with the database? Ask the database a question using an IM client and the database will (try to) answer to that question...

I started off with downloading and installing the Oracle-XMPP code (XMPP stands for Extensible Messaging and Presence Protocol). Because I needed my own XMPP-server, I also downloaded and installed OpenFire. One of the options when installing OpenFire is to use an Oracle Database for storing the data (using a OJDBC driver). In the OpenFire schema there is a table called ofoffline, used to store messages send to users that are offline. By defining a user (called 'oracle'), that is always offline, I can get "my" messages there. I also wrote a trigger on that table to handle the requests. And the result is someting like this:
How cool is that?
Of course you can (and should) modify the parsing of the query to make it more userfriendly - and not vulnerable to SQL-Injection. But you can chat with your database using this stuff!
Location: Arnhem, Nederland

Comments

Lucas Jellema said…
Nice indeed! (also nice to have provided some inspiration). Well done, Roel!
10:33 pm
Filipe Silva said…
Great ideia!
1:28 am
Post a Comment

Popular posts from this blog

Filtering in the APEX Interactive Grid

By
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 old Employ
1 comment
Read more

apex_application.g_f0x array processing in Oracle 12

By
If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one: then you disable the " Escape special characters " property and the result is an updatable multirecord form. That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for
Post a Comment
Read more

Stop using validations for checking constraints !

By
 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
Post a Comment
Read more