db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1313) SUR: Use DRDA's extended diagnostic to send ROW_UPDATED and ROW_DELETED warnings.
Date Thu, 08 Jun 2006 00:21:31 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1313?page=comments#action_12415241 ] 

Dag H. Wanvik commented on DERBY-1313:
--------------------------------------

The way I interpret the description of DIAGLVL,
the implementation is compliant, even after DERBY-1374, 
cf. this section of the specification of DIAGLVL:

"If DIAGLVL0 is specified or the default value is provided, the 
SQLDIAGGRP is returned as a null group. The DIAGLVL0 may 
be upgraded by the target server to DIAGLVL1 when executing
an EXCSQLSTT command or an OPNQRY command which 
generates multiple error or warning conditions processing
 the command."

After DERBY-1374 (a fix to this patch) the client no longer asks for 
DIAGLVL2 as did this patch (since that broke old servers, cf. 
explanation by Fernanda in DERBY-1374), but it seems it is ok (according 
to the above), for the server to send at DIAGLVL1.

Of course, presently only the two warnings used for DERBY-1313 are ever
sent using level 1 but I think that's OK as far as compliance with 
the protocol goes (server's discretion how much to send)

> 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, derby-1313v2.diff, derby-1313v2.stat,
derby-1313v3.diff, derby-1313v3.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


Mime
View raw message