Problems with SVG line charts based on PL/SQL returning SQL

Question

Dear all - I wonder if anyone can tell me whether this problem is likely to be fixed at some point?
It relates to the fact that you can't get more than one series on a chart where the SQL is returned from PL/SQL.
It is a huge issue for us when trying to create complex, dynamic charts, which are simple enough in PL/SQL, but end up quite nightmarish in pure SQL.
Although we have implemented Maani SWF (Flash) charts as a workaround, users don't like them as there's no 'save as...' or copy+paste and they seem to print very badly indeed.
Here's part of a post from last May with more detail:
"If I take a really simple table like this:
CREATE TABLE "CHART_TEST"
( "X" DATE NOT NULL ENABLE,
"Y" NUMBER(5,0) NOT NULL ENABLE,
CONSTRAINT "CHART_TEST_PK" PRIMARY KEY ("X") ENABLE
and populate it with:
X Y
2006-01-01T00:00:00 1
2006-02-01T00:00:00 2
2006-03-01T00:00:00 3
2006-04-01T00:00:00 4
2006-05-01T00:00:00 5
2006-06-01T00:00:00 6
2006-07-01T00:00:00 7
2006-08-01T00:00:00 8
2006-09-01T00:00:00 9
2006-10-01T00:00:00 10
I can create a chart with a single series using syntax something like:
begin
return 'select null link, x label, y value
from chart_test';
end;
and this works fine. However, if I add a second series:
begin
return 'select null link, x label, (y + 1) value
from chart_test';
end;
then the whole of the chart region blanks out.
There's an example at:
http://htmldb.oracle.com/pls/otn/f?p=15491:1"
Many thanks,
John.

Answer 1

On some, but not all SVG line charts, I had trouble when some values are ZERO.
Putting a CASE WHEN var = 0 then 0.05 ELSE var END in the select statement
fixed those situations.
I had missing lines when the number of data points in a series exceeded the default number of 15, and I did not set in the series configuration to a number equal to or higher that the number of data points in that series.
And I had one instance, where a couple missing lines reappeared when I exited
the browser and app completely and restarted the app.
All these comments apply to ver 1.6x and 2.0x