Project

General

Profile

Bug #4217

Report Viewer - "nil" not rendering consistently/correctly

Added by ben leinfelder about 10 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
Normal
Category:
reporting
Target version:
Start date:
07/01/2009
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4217

Description

When outputting arrays of numbers and booleans that contain "nil" entries in R, they are not converted to NULL for use in Kepler/ptII


Related issues

Blocked by Kepler - Bug #4197: Waterflow TPC demo - tracking bugResolved06/29/2009

History

#1 Updated by ben leinfelder about 10 years ago

The PDF seems to render "nil" as "nil" whereas the AWT rendering (from Apache-FOP) sometimes shows a huge integer instead. I believe it's something to do with how the AWT is using components- maybe the column (int) is confused by this? Also seeing some "NaN" entries in a different column (double)

#2 Updated by ben leinfelder about 10 years ago

After some digging, I'm going to conclude that this is being introduced by the "deep copy" serialization technique for creating a ReportInstance from a ReportLayout.

2147483647 = Integer.MAX_VALUE like IntToken.NIL

#3 Updated by ben leinfelder about 10 years ago

added special handling when we have IntToken.NIL in the report instance

NEED TO COMMIT TO BRANCH

#4 Updated by ben leinfelder about 10 years ago

This is also happening for DoubleTokens - but they show as NaN rather than nil - which I believe is acceptable.
BooleanTokens loose their nil-ness and become false which may be misleading in some situations - but typically it corresponds to rows where there are null data and you can infer that false is inconclusive. At any rate, we're stuck with that.

#5 Updated by ben leinfelder about 10 years ago

committed to the branch.

#6 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 4217

Also available in: Atom PDF