db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1658) Too short streams passed in through JDBC are handled differently in client and embedded
Date Wed, 09 Aug 2006 23:28:13 GMT
Too short streams passed in through JDBC are handled differently in client and embedded
---------------------------------------------------------------------------------------

                 Key: DERBY-1658
                 URL: http://issues.apache.org/jira/browse/DERBY-1658
             Project: Derby
          Issue Type: Improvement
          Components: JDBC, Network Client, Network Server
    Affects Versions: 10.2.0.0
            Reporter: Kristian Waagan


In the embedded driver, insertion is aborted if the stream used as source is shorter then
the specified length.
In the client driver, the stream is padded and the insertion is completed. Note that an exception
is thrown here as well, but the data is inserted into the database and can be retrieved after
the exception have been caught.
If anyone has information about why this was done, it would be nice. Could it be that the
DRDA protocol can't handle this easily?

This difference was discovered while writing tests, and the impact on the test code is not
good as you need special code for running it with the client.

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