Like me, some people may have gotten excited about using XMLFOREST in SQLX, only to find that NULL values result in altogether MISSING elements, as opposed to simply EMPTY elements. Many times avoiding printing elements with null values is desired functionality, but in some cases the consumer of the XML might require those elements to generated anyways, with a null value (i.e. [tagname][/tagname]).

Thus, I have found it is easiest to use XMLELEMENT instead of XMLFOREST for these cases. Note: IBM offers a directive to print empty elements for null values, but until Oracle implements such a feature, your best best is probably to leverage XMLELEMENT:

1
2
3
4
5
6
7
8
9
10
11

SELECT xmlforest(a).getstringval() FROM (SELECT 1 a FROM dual);
--returns: <A>1</A>
 
SELECT xmlforest(a).getstringval() FROM (SELECT NULL a FROM dual);
--returns: null
 
SELECT xmlelement("A", a).getstringval() FROM (SELECT 1 a FROM dual);
--returns: <A>1</A>
 
SELECT xmlelement("A", a).getstringval() FROM (SELECT NULL a FROM dual);
--returns: <A></A>

I just can’t wait for Flash on Android…and for Apple’s hand to [hopefully] get forced into supporting Flash as well.

I have seen multiple custom solutions and packaged applications store their SQL outside of stored procedures. I am focusing this article on custom enterprise solutions, which I feel is one of the fastest growing areas in development. Some people who choose to store SQL outside of their database have touted database independence/abstraction, others easier maintenance, and I’m sure many other “excuses” have been communicated. In my opinion, if you have 1) a custom enterprise application and 2) an Oracle database(s) as the backend, all of your SQL — and associated DB logic — should be written, stored, maintained, etc. within Oracle stored procedures. I can dream up very unique scenarios where a valid argument could possibly begin to be made to keep SQL outside — but I think 99% of places that have done this, or will be considering this, really should have kept SQL inside their DB.

I’d like to hear your reasons for maintaining your Oracle SQL outside of Stored Procedures.

I have been somewhat enamored by Google Apps and its potential. Many enterprises have been happy with Exchange for mail, calendaring, contacts, and more. I have been one of those people. However, I have found Google Apps to be getting better and better for use in the enterprise and I will not be surprised to see it begin to take significantly larger chunk of market share from Microsoft over time.

I have been tasked with coming up with a modularized approach for logically separating out an extensive Flex application I am developing. I see Flex 3.4 might have some features I can take advantage of.

The site search game is changing with Google CSE.

We have recently been working on and completed an entire Oracle Fusion Middleware 11g environment setup for a customer:

• Identity Management
• WebCenter (Framework and Services)
• SOA Suite
• UCM

This article is part of the recent work short blurb series.

I had the age-old requirement today to build a data-driven, dynamic form…only this time with my RIA written in Adobe Flex. It was just as fun as normal, and this time it looks very nice with the RIA feel.

This article is part of the recent work short blurb series.

A few of us have got some writer’s cramp (is there such a thing when typing?) from writing an excellent WebCenter 11g book.

If there were a buzz word that could compete with the speed to fame, breadth of use (and misuse), and popularity of “Web 2.0″, it would have to be “Cloud Computing”.