db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4553) In ij GETCURRENTROWNUMBER directly writeits result to output
Date Fri, 19 Feb 2010 19:38:28 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen updated DERBY-4553:
--------------------------------------

    Issue & fix info: [Newcomer]  (was: [Patch Available, Newcomer])
       Fix Version/s: 10.6.0.0

The tests ran cleanly in my environment. Committed revision 911952.

> In ij GETCURRENTROWNUMBER directly writeits result  to output
> -------------------------------------------------------------
>
>                 Key: DERBY-4553
>                 URL: https://issues.apache.org/jira/browse/DERBY-4553
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>            Reporter: Sylvain Leroux
>            Assignee: Sylvain Leroux
>            Priority: Trivial
>             Fix For: 10.6.0.0
>
>         Attachments: DERBY-4553.patch, DERBY-4553_2.patch, DERBY-4553_repro.patch
>
>
> In ij, the statement GETCURRENTROWNUMBER directly write its result to output instead
of returning it:
> Here are the faulty lines in ij.ij, method GetCurrentRowNumber():
> 	...
> 	LocalizedResource.OutputWriter().println(utilInstance.getCurrentRowNumber(rs));
> 	return null;
> This interferes with testing - and possibly with any external tool using the ij.ij parser.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message