You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <de...@db.apache.org> on 2006/08/10 01:28:13 UTC

[jira] Created: (DERBY-1658) Too short streams passed in through JDBC are handled differently in client and embedded

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

[jira] Closed: (DERBY-1658) Too short streams passed in through JDBC are handled differently in client and embedded

Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristian Waagan closed DERBY-1658.
----------------------------------

    Fix Version/s: 10.6.1.0
       Resolution: Fixed

Fixed by DERBY-2017.

> Too short streams passed in through JDBC are handled differently in client and embedded
> ---------------------------------------------------------------------------------------
>
>                 Key: DERBY-1658
>                 URL: https://issues.apache.org/jira/browse/DERBY-1658
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC, Network Client, Network Server
>    Affects Versions: 10.2.1.6
>            Reporter: Kristian Waagan
>             Fix For: 10.6.1.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (DERBY-1658) Too short streams passed in through JDBC are handled differently in client and embedded

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden updated DERBY-1658:
----------------------------------

    Derby Categories: [Embedded/Client difference]

> Too short streams passed in through JDBC are handled differently in client and embedded
> ---------------------------------------------------------------------------------------
>
>                 Key: DERBY-1658
>                 URL: https://issues.apache.org/jira/browse/DERBY-1658
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC, Network Client, Network Server
>    Affects Versions: 10.2.1.6
>            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.
-
You can reply to this email to add a comment to the issue online.