db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1473) Add cut-off and truncation logic to streaming classes in the embedded driver
Date Wed, 23 Aug 2006 11:57:14 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1473?page=comments#action_12429977 ] 
Knut Anders Hatlen commented on DERBY-1473:

Thanks for addressing my comments, Kristian!

You removed the else clause in RawToBinaryFormatStream's constructor,
but I think you could also remove the if check, since the condition
will always be true.

Could you also elaborate on how the new class DerbyIOException is
going to be used? As it is now, it is only thrown, and not caught
anywhere. The javadoc for the class says:

  Without this distinction, the user would not be able to easily write
  <code>catch</code>-blocks to handle specific errors happening when
  reading streams.

Does this mean our users should check for a DerbyIOException?

> Add cut-off and truncation logic to streaming classes in the embedded driver
> ----------------------------------------------------------------------------
>                 Key: DERBY-1473
>                 URL: http://issues.apache.org/jira/browse/DERBY-1473
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions:
>            Reporter: Kristian Waagan
>         Assigned To: Kristian Waagan
>             Fix For:
>         Attachments: derby-1473-1a-streaming.diff, derby-1473-1a-streaming.stat, derby-1473-1b-streaming.diff,
derby-1473-2a-streamingtests.diff, derby-1473-2a-streamingtests.stat, derby-1473-2b-streamingtests.diff
> When streaming data to Derby, the application stream will be wrapped in a Derby-specific
stream to convert the data to the correct representation. At a minimum, this consists of getting
the data to the on-disk format used by Derby.
> The wrapping stream can be extended to provide the following features at an earlier stage:
>  a) Data cut-off when the maximum allowed size is exceeded
>  b) Truncation of trailing blanks where allowed
> Both features can reduce the amount of data needed to be kept in memory on insertion.
> Implementing this will require additional column/data type information in the streaming
class(es). The implementation must be able to handle streams for which the length is specified
and also streams with unknown/unspecified length.

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


View raw message