Hi All,
I modified the BasecolumnNode class's IsEquivalent method to add the
monitor method... But still when executing test.lang.__Suite, the log
doesn't show any trace of the newly added trace , i am attaching the
patch and the __Suite output to the jira. Please let me know any
other options if they exist..
With Regards
Jayaram
On Tue, Feb 8, 2011 at 9:42 AM, Jayaram Subramanian <rsjay1976@gmail.com> wrote:
> Hi Knut,
> I am interested in taking up this task. Let me know your views on the same.
>
> With Regards
> Jayaram
>
> On Tue, Feb 8, 2011 at 6:17 AM, Knut Anders Hatlen (JIRA)
> <jira@apache.org> wrote:
>>
>> [ https://issues.apache.org/jira/browse/DERBY-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991950#comment-12991950
]
>>
>> Knut Anders Hatlen commented on DERBY-5010:
>> -------------------------------------------
>>
>> The current code looks wrong and the suggested fix looks right.
>>
>> None of our regression tests seem to exercise this code path, though. It would be
good if someone could come up with a statement that caused this code to be executed so that
we can verify that it behaves as expected after the proposed changes.
>>
>>> [patch] bad equivalence check
>>> -----------------------------
>>>
>>> Key: DERBY-5010
>>> URL: https://issues.apache.org/jira/browse/DERBY-5010
>>> Project: Derby
>>> Issue Type: Bug
>>> Components: SQL
>>> Affects Versions: 10.7.1.1
>>> Reporter: Dave Brosius
>>> Priority: Trivial
>>> Fix For: 10.8.0.0
>>>
>>> Attachments: bad_equivalence_check.diff
>>>
>>> Original Estimate: 1h
>>> Remaining Estimate: 1h
>>>
>>> code attempts to compare two BaseColumnNodes but doesn't compare the tableName
correctly.
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>
>>
>>
>
|