Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <260310590.1225883384269.JavaMail.jira@brutus>
Date: Wed, 5 Nov 2008 03:09:44 -0800 (PST)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-3936) Add CharacterStreamDescriptor
In-Reply-To: <1437825848.1225883024422.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristian Waagan updated DERBY-3936:
-----------------------------------

          Component/s: JDBC
          Description: 
A set of state information is required about byte streams representing characters to be able to handle them properly.

The basic pieces of information are:
 - is bufferable
 - is position aware
 - data offset
 - current byte position
 - current char position
 - byte length
 - char length

Additional info:
 - encoding
 - max allowed length
 - bytes per char information

The information is chosen with UTF8Reader in mind, and the plan is to pass a CharacterStreamDescriptor instance to the constructor to allow the reader to configure itself appropriately. The information is expected to be valid only at a specific point in time, as some of it will change as soon as the reader starts working with the underlying stream.
             Priority: Minor  (was: Major)
    Affects Version/s: 10.5.0.0

> Add CharacterStreamDescriptor
> -----------------------------
>
>                 Key: DERBY-3936
>                 URL: https://issues.apache.org/jira/browse/DERBY-3936
>             Project: Derby
>          Issue Type: Sub-task
>          Components: JDBC
>    Affects Versions: 10.5.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>
> A set of state information is required about byte streams representing characters to be able to handle them properly.
> The basic pieces of information are:
>  - is bufferable
>  - is position aware
>  - data offset
>  - current byte position
>  - current char position
>  - byte length
>  - char length
> Additional info:
>  - encoding
>  - max allowed length
>  - bytes per char information
> The information is chosen with UTF8Reader in mind, and the plan is to pass a CharacterStreamDescriptor instance to the constructor to allow the reader to configure itself appropriately. The information is expected to be valid only at a specific point in time, as some of it will change as soon as the reader starts working with the underlying stream.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.