[
https://issues.apache.org/jira/browse/DERBY-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457170#comment-13457170
]
Kathey Marsden commented on DERBY-5920:
---------------------------------------
The change was made because we got various reports on the user list from users
trying to use clients that were not or no longer supported by the vendors with
Derby, most prominently the DB2 runtime client. The problem was that folks
could go down the dead end path to a certain point where it would seem to work
until it didn't and failed with some awful stack trace and waste a lot of time
debugging and thinking they could work through it when as I said it was a dead
end. It seemed better to put up a clear barrier from the start instead of
inviting folks down that dead end path.
Also around the same time there were discussions on the dev list of using DRDA
as more of a guideline than a standard. I don't particularly agree with that
position and would like to see things get back in the standard, but sometimes
that process can take a very long time (as we saw with DERBY-728) so I can
understand the frustration of going through it. If that is to be the
approach. It will be important for other clients to be involved in the
community and add their support specifically and monitor changes that occur.
Also having specific supported contents e.g. SIG in the code by name might
give developers considering changes pause to consider the impact, not that they
have to but they might.
> 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: 10.9.1.0
> 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
