You can view the issue detail at the following URL:
<http://nagoya.apache.org/scarab/issues/id/TRQS51>
Type : Defect
Issue Id : TRQS51
Reported by: thierry lach
thierrylach - ([EMAIL PROTECTED])
Details:
Summary: Datadump does not recognize null columns properly
Description: Datadump does not appear to recognize null columns.
Creating a datadump using the torque bundled with the Scarab project, I get the
following XML node created.
<AttributeValue ValueId="123" IssueId="120" AttributeId="7" NumericValue="0"
OptionId="54" UserId="54" Value="High" Deleted="0"/>
Using Oracle's database query tool, I see:
SQL> set null <<null>>
SQL> list
1* select * from scarab_issue_attribute_value where value_id = 123
SQL> /
VALUE_ID ISSUE_ID ATTRIBUTE_ID NUMERIC_VALUE OPTION_ID USER_ID
---------- ---------- ------------ ------------- ---------- ----------
VALUE
----------------------------------------------------------------------------------------------------
DELETED
----------
123 120 7 0 54 <<null>>
High
0
SQL>
indicating that the userid is in fact null, while the XML node indicates it as being
54. By looking at other such unusual data values (including text strings in numeric
fields), it appears that while enumerating through the fields, any null field
duplicates the previous field contents.
Status: New
Database: Oracle
Priority: High
--
To unsubscribe, e-mail: <mailto:turbine-torque-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:turbine-torque-dev-help@;jakarta.apache.org>
