I think that the alternative is that we'd need to do this string processing in Java code,
rather than in the SQL.
But, in fact, I think this may not be very hard. For instance, I believe that
will already automatically do the equivalent of the "TRIM(CHAR(NO_OPENS))"
processing. So all we're really talking about here is doing something like:
"||"+rs.getString("no_opens") + "||"
Although, it strikes me that we should eliminate the "||" processing as well, as
I suspect these are just markers that will be used later in the code to parse
the values apart, which doesn't seem like the right approach either. It seems
like we should make the ResultSet object available to the bit of code which
needs to fetch the value of the NO_OPENS column, so that code can just do
the getInt() or getString() call itself, directly.
I understand that this would mean a bit of refactoring of the current PlanExporter
code, so we should study it some more.