db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4034) Document database name and attribute length and character set limitations for network client
Date Thu, 02 Jul 2009 14:21:47 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726494#action_12726494
] 

Kim Haase commented on DERBY-4034:
----------------------------------

Thanks, Kathey, this is very helpful information -- I hadn't been sure what to do about this
issue.

I have only a couple of non-technical suggestions --

The new paragraph is all on one continuous line -- it would be nice if you could break it
into <80 character lines for readability in text editors.

I would suggest changing "Driver" to "driver" and "starting network server" to "starting the
Network Server" for consistency with usage elsewhere in the topic.

You might think about changing "single byte characters" to "single-byte characters" to make
the distinction from multibyte characters clearer.

> Document database name  and attribute length and character set limitations for network
client
> ---------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4034
>                 URL: https://issues.apache.org/jira/browse/DERBY-4034
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.5.1.1
>            Reporter: Kathey Marsden
>            Assignee: Kathey Marsden
>            Priority: Minor
>         Attachments: cadminappsclient.html, derby-4034_diff.txt
>
>
> With network client, the database name and following attributes must be:
> 1) Limited to length of 255 bytes when converted to EBCDIC.
> 2) Limited to single byte characters that can be converted to EBCDIC encoding. 
> DERBY-728 proposes that we support UTF-8 encoding so that multibyte characters.  After
that is fixed the 255 byte limit (when converted to UTF-8) will still remain.

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


Mime
View raw message