db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5920) Network Server should accept DRDA connections from drivers with the StarQuest PRDID "SIG"
Date Mon, 10 Sep 2012 16:44:07 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452127#comment-13452127

Kathey Marsden commented on DERBY-5920:

If someone would like to add  StarQuest as a recognized client, there are a few areas to consider.

First are  the areas where stored procedures or SQLSET are used to implement JDBC functionality.
 These are not deviations from the protocol standard per say but just how things like database
metadata and LOB support and setQueryTimeout  are implemented.

The second area is areas where we have extended the standard. I have not added these personally
so don't know a lot about what has been done, but I think  it applies to UDT's. I am not sure
what else.

The third is areas where we have out and out deviated. As the protocol interface is not part
of our public API, we have not been strict on this point. One example I can think of where
this might happen is: https://issues.apache.org/jira/browse/DERBY-4805 (not implemented yet).

If you would like to submit a patch to add SIG I personally would not be against that. I would
suggest that you modify the Derby  tests to support  the  Starquest Driver support and then
run them to see what is broken.   Then really you would want to commit to running those tests
every release or adding in conditional code to have StarQuest connections take the path of
older clients.  This code exists for older Derby clients so you could go the same path.

I know that is not a lot of detail but if you would like to pursue adding StarQuest support
to Derby.  I am sure there are people in the community that would be willing to help fill
in the blanks.  I have to say it is hard though to keep a proprietary codeline in sync with
an open source one.  If you can frame your  questions to the community in terms of the Derby
source code, perhaps giving an example with Derby client that would be probably most productive.



> Network Server should accept DRDA connections from drivers with the StarQuest PRDID "SIG"
> -----------------------------------------------------------------------------------------
>                 Key: DERBY-5920
>                 URL: https://issues.apache.org/jira/browse/DERBY-5920
>             Project: Derby
>          Issue Type: Improvement
>          Components: Network Server
>    Affects Versions:
>         Environment: Any
>            Reporter: David Brown
>              Labels: DRDA, SIG, StarQuest, StarSQL, client, network
> Background - Refer to DERBY-5565
> "Derby Network Server has been changed to reject client connections from clients that
are not Derby Network Client (Those that do not send PRDID starting with DNC).
> Rationale for Change: There are currently no known supported network clients for Derby
Network Server other than Derby Network Client."
> This is incorrect - StarQuest Ventures has a shipping DRDA-compliant network client "StarSQL
for Java" that has supported Derby since August 2008. It is listed at http://wiki.apache.org/db-derby/UsesOfDerby.
> This change means that we can now only use an older version of Derby until our PRDID
is added.
> Our PRDID is SIG - see http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/index.jsp?topic=%2Fddp%2Frbal1exitpgms.htm
for a list of DRDA PRDID's.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message