[ http://issues.apache.org/jira/browse/DERBY-1313?page=all ]
Fernanda Pizzorno updated DERBY-1313:
-------------------------------------
Attachment: derby-1313.diff
derby-1313.stat
In the server side, SQLDIAGGRP had been implemented on the DRDAConnThread, but
it was commented out. This implementation has been uncommented in this patch
and SQLDIAGGRP are now sent if the client requests diagnostic level !=
SQLDIAG0. The implementation of SQLDIAGGRP has also been changed so that only
ROW_UPDATE AND ROW_DELETED warnings will be sent to the client.
The client has been changed so as to request diagnostic level SQLDIAG2 (which
means that SQLDIAGGRP will be sent by the server, but the error message will
not be sent), and to be able to parse SQLDIAGGRP.
A test has been added to SURTest that verifies that a row can return true for
both rowUpdated() and rowDeleted().
Can someone please review this patch?
Thank you in advance :-).
> SUR: Use DRDA's extended diagnostic to send ROW_UPDATED and ROW_DELETED
> warnings.
> ---------------------------------------------------------------------------------
>
> Key: DERBY-1313
> URL: http://issues.apache.org/jira/browse/DERBY-1313
> Project: Derby
> Type: Bug
> Components: JDBC
> Reporter: Fernanda Pizzorno
> Assignee: Fernanda Pizzorno
> Attachments: derby-1313.diff, derby-1313.stat
>
> Detectability of own changes is implemented in the client using warnings cf
> the write-up for DERBY-775. When a row has been deleted and/or updated, a
> warning will be sent to the client to indicate that fact. Presently, only one
> warning can be sent each time a data row is sent from to the client, that
> means that some warnings may be lost. Using extended diagnostic allows us to
> send several warnings for each data row.
> I propose to use extended diagnostics to send ROW_UPDATED and ROW_DELETED
> warnings when necessary. This may later be extended for other warnings, but I
> do not plan to do it as a part of the work in this issue.
--
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
