Author: kmarsden
Date: Mon Jul 13 18:30:30 2009
New Revision: 793651

URL: http://svn.apache.org/viewvc?rev=793651&view=rev
Log:
DERBY-4034 Document database name and attribute length and character set limitations for network client

Modified:
    db/derby/docs/branches/10.5/src/adminguide/cadminappsclient.dita

Modified: db/derby/docs/branches/10.5/src/adminguide/cadminappsclient.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/branches/10.5/src/adminguide/cadminappsclient.dita?rev=793651&r1=793650&r2=793651&view=diff
==============================================================================
--- db/derby/docs/branches/10.5/src/adminguide/cadminappsclient.dita (original)
+++ db/derby/docs/branches/10.5/src/adminguide/cadminappsclient.dita Mon Jul 13 18:30:30 2009
@@ -32,6 +32,19 @@
 </codeblock>where the <codeph>&lt;URL attribute&gt;</codeph> is either a <ph
 conref="../conrefs.dita#prod/productshortname"></ph> embedded or network
 client attribute.</p>
+
+<p>
+For both driver and DataSource access, the database name (including path), 
+user, password  and other attribute values must consist of single-byte 
+characters that can be converted to EBCDIC.  The total byte length of the 
+database name plus attributes when converted to EBCDIC must not exceed 255 
+bytes. You may be able to work around this restriction for long paths or 
+paths that include multibyte characters by setting the 
+<codeph>derby.system.home</codeph> system property when starting Network 
+Server and accessing the database with a relative path that is shorter and 
+does not include multibyte characters.
+</p>
+
 <table><title>Standard JDBC DataSource properties</title>
 <tgroup cols="5"><colspec colname="col1" colwidth="110*"/><colspec colname="col2"
 colwidth="49*"/><colspec colname="col3" colwidth="106*"/><colspec colname="COLSPEC0"