db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-982) sysinfo api does not provide genus name for client
Date Sat, 15 Jul 2006 08:24:14 GMT
     [ http://issues.apache.org/jira/browse/DERBY-982?page=all ]

Andrew McIntyre updated DERBY-982:

    Attachment: derby-982_v3.diff

Attaching updated patch for this issue. Test has been rewritten as a junit test.

Currently, the test for sysinfo.getInfo() is commented out because I was having a problem
piping the output from the PrintWriter assigned to sysinfo.getInfo() to a BufferedReader that
reads the first line from that PrintWriter. I'm not that familiar with piped readers/writers,
so perhaps someone can spot what I'm doing wrong and fix that particular test. The problem,
when the test is uncommented, is that the PipedReader hangs in a native method.

That could be handled in a followup patch, though. As it is, I think this patch could be committed
as-is for this issue.

> sysinfo api does not provide genus name for client
> --------------------------------------------------
>                 Key: DERBY-982
>                 URL: http://issues.apache.org/jira/browse/DERBY-982
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions:
>            Reporter: Kathey Marsden
>         Assigned To: Andrew McIntyre
>             Fix For:
>         Attachments: derby-982.diff, derby-982_v2.diff, derby-982_v3.diff
> The sysinfo api does not provide access to the genus name for client to allow applications
to retrieve information from sysinfo about the client information.
> http://db.apache.org/derby/javadoc/publishedapi/org/apache/derby/tools/sysinfo.html
> Note: Currently ProductGenusNames has a genus name for network server but network server
is closely tied to  the engine so should always have the same version.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message