[
https://issues.apache.org/jira/browse/DERBY-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499358
]
Myrna van Lunteren commented on DERBY-1610:
-------------------------------------------
Hi,
This issue is one of several that is in progress, however, if I understand it
correctly, a change that might impact existing applications has already gone
in, and will be in for 10.3.
I too find it important to document this change in behavior in the 10.3 release
notes.
The way it works, though, is that unless we do something, nothing will show up
in the release notes on this.
We have a number of choices;
1. adjust/falsify history and change the comment for revision 453886 to belong
to for instance DERBY-1501, or maybe DERBY-1494...
2. close this bug as fixed in 10.3 and add the release note here.
I vote for 2.
I propose the following:
- log a new bug (if not done already) for the issue with the type
incompatibility of OUT parameters for stored procedures and link this new bug
to DERBY-310.
- close this bug as fixed in 10.3.
- removing the existing application impact check from DERBY-1501 because no
change specific to that bug went into subversion, so a release note seems
contrary.
I understand your concern about giving the impression that all type differences
were resolved, but then again, I don't think a release note about a fix is the
appropriate place for that. So, I suggest we use verbage that suggests more
differences may exist.
I propose something like the following for the release note, please review &
correct:
------------------------------
Summary of Change
Derby's Client implementation will return an appropriate error, matching the
behavior with Embedded in the a number of situations related to
PreparedStatement.setNull(int, int).
Symptoms Seen by Applications Affected by Change
In a number of situations, Derby's client implementation behaved differently
from the Embedded implementation:
1. setNull(LONGVARCHAR) on parameter of type CHAR FOR BIT DATA (Types.BINARY).
In previous releases, the Client succeeds, embedded fails (state 22005).
2. setNull(LONGVARBINARY) on parameter of type CHAR FOR BIT DATA (Types.BINARY).
In previous releases, Embedded succeeds, client fails (state 22005).
3. setNull(LONGVARBINARY) on parameter of type VARCHAR FOR BIT DATA
(Types.VARBINARY).
In previous releases, Embedded succeeds, client fails (state 22005).
4. setNull(BINARY) on parameter of type LONG VARCHAR FOR BIT DATA
(Types.LONGVARBINARY)
In previous releases, Embedded succeeds, client fails (state 22005).
5. setNull(TIME) on parameter of TIMESTAMP.
In previous releases, Client succeeds, embedded fails (state 22005).
Incompatibilities with Previous Release
Now, in the cases indicated above, the client and Embedded implementation show
the behavior previously shown only with Embedded.
Rationale for Change
Derby's Client implementation and Embedded implementation should behave the
same way from the point of view of an application whenever possible.
Application Changes Required
Applications relying on the Client behaving in the old way will have to be
adjusted.
------------------------------
If I do not hear objections, I'll proceed with this plan.
> Resolve difference of type compatibility between Embedded and
> NetworkServer/NetworkDriver
> -----------------------------------------------------------------------------------------
>
> Key: DERBY-1610
> URL: https://issues.apache.org/jira/browse/DERBY-1610
> Project: Derby
> Issue Type: Bug
> Components: Network Client, Network Server
> Reporter: Tomohito Nakayama
> Assigned To: Tomohito Nakayama
> Attachments: derby-1610-jdk16.diff, DERBY-1610.diff,
> DERBY-1610_2.diff, DERBY-1610_3.diff, DERBY-1610_4.diff, DERBY-1610_5.diff,
> DERBY-1610_6.patch, DERBY-1610_7.patch, DERBY-1610_7_regressionfix.patch,
> DERBY-1610_7_regressionfix_2.patch, DERBY-1610_7_regressionfix_2_2.patch,
> DERBY-1610_7_regressionfix_2_3.patch, parameterMapping.diff,
> parameterMapping.diff,
> parameterMapping.diff.betweenEmbedded_and_NetworkServerNetworkClient,
> parameterMapping.out.7.diff, parameterMapping.out.diff,
> parameterMapping_3.diff, TestNullChar.java, TestTypeCompatibility.java,
> XCL12.diff
>
>
> There exists difference of type compatibility between Embedded and
> NetworkServer/NetworkClient.
> This issue tries to resolve it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
