[
https://issues.apache.org/jira/browse/DERBY-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3936:
-----------------------------------
Fix Version/s: 10.5.0.0
Thanks Knut Anders.
I committed patch 1b to trunk with revision 718936.
Depending on how things play out, I might consider adding a reference to the
stream in the descriptor object.
I'll leave the issue open until I have a clearer view of how, and where, the
descriptor object will be used.
If anyone has opinions on keeping a reference to the described stream in the
descriptor, please add a comment.
> 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
> Fix For: 10.5.0.0
>
> Attachments: derby-3936-1a-CharacterStreamDescriptor.diff,
> derby-3936-1b-CharacterStreamDescriptor.diff
>
>
> 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.
