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