db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Saurabh Vyas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2017) Client driver can insert and commit partial data when a LOB stream throws IOException or does not match the specified length
Date Thu, 07 Dec 2006 18:42:22 GMT
    [ http://issues.apache.org/jira/browse/DERBY-2017?page=comments#action_12456523 ] 
            
Saurabh Vyas commented on DERBY-2017:
-------------------------------------

Well with this approach, the two configurations will behave differently. In embedded mode,
in case of error, only the erroneous statement will make no effect on database and rest of
the statements in transaction will remain unaffected by the error. Whereas in network mode,
in case of error, the complete transaction will be rolled back so that the database can remain
in consistent state (which is not handled currently as pointed out in repro).

I tried searching options from DRDA specifications but the DO_NOT_CONTINUE_ON_ERROR flag provided
in DSS header will not be of any use as the error is at client side. Thanks to Julo for pointing
this out.

Apart, as mentioned by Knut also, the closest we can get as long as we're using DRDA. Can
we try any other approach for this.
Comments/Suggestions.

> Client driver can insert and commit partial data when a LOB stream throws IOException
or does not match the specified length
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2017
>                 URL: http://issues.apache.org/jira/browse/DERBY-2017
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client
>    Affects Versions: 10.2.1.6
>            Reporter: Knut Anders Hatlen
>         Assigned To: Saurabh Vyas
>             Fix For: 10.3.0.0, 10.2.2.0
>
>         Attachments: Derby_2017_v1.diff, Derby_2017_v1.stat, StreamErrRepro.java
>
>
> When a LOB stream throws an exception or does not match the specified length, the client
driver does not raise an exception until it has finished executing the statement. Therefore,
the statement will be executed (and possibly committed) on the server even though the client
reports that the statement failed.

-- 
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