db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-982) sysinfo api does not provide genus name for client
Date Thu, 13 Jul 2006 12:11:31 GMT
    [ http://issues.apache.org/jira/browse/DERBY-982?page=comments#action_12420855 ] 

Kristian Waagan commented on DERBY-982:

I had a look at the patch, and also downloaded it and tried running the test.
The patch applies cleanly, but the test fails.
Is it supposed to only be run on release/snapshot distributions? I'm aksing, because it seems
the test is dependent on a build target in 'tools/release/build.xml'. I can't see the test
have been enabled in any suites either.

The diff tells me that only the getX() and getX(sysinfo.DBMS) calls are returning correct
results. The rest return "<no name found>" or -1.
Since I'm not sure if I'm running the test correctly, can somebody that knows how to run the
test report their findings?

If the test is actually working (when run the correct way), I think the patch could be committed.
It has been around for a while.

> sysinfo api does not provide genus name for client
> --------------------------------------------------
>          Key: DERBY-982
>          URL: http://issues.apache.org/jira/browse/DERBY-982
>      Project: Derby
>         Type: Bug

>   Components: Tools
>     Versions:
>     Reporter: Kathey Marsden
>     Assignee: Andrew McIntyre
>      Fix For:
>  Attachments: derby-982.diff, derby-982_v2.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:
For more information on JIRA, see:

View raw message