db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Satheesh Bandaram (JIRA)" <derby-...@db.apache.org>
Subject [jira] Closed: (DERBY-50) getMaxColumnNameLength() database metadata function returns incorrect value.
Date Sat, 04 Jun 2005 20:52:44 GMT
     [ http://issues.apache.org/jira/browse/DERBY-50?page=all ]
     
Satheesh Bandaram closed DERBY-50:
----------------------------------


Patch submitted.

> getMaxColumnNameLength() database metadata function returns incorrect value.
> ----------------------------------------------------------------------------
>
>          Key: DERBY-50
>          URL: http://issues.apache.org/jira/browse/DERBY-50
>      Project: Derby
>         Type: Bug
>   Components: JDBC
>     Versions: 10.0.2.0
>  Environment: Generic issue. Was reproduced on Windows platform.
>     Reporter: Satheesh Bandaram
>      Fix For: 10.0.2.0

>
> Database Metadata function getMaxColumnNameLength() should return 30. It incorrectly
returns 128. Derby restricts maximum column name length to be 30. Similarly, the following
metadata functions also return incorrect values:
> getMaxCursorNameLength() = 18
> getMaxSchemaNameLength() = 30
> getMaxProcedureNameLength() = 128
> getMaxTableNameLength() = 128
> getMaxUserNameLength() = 30
> Note, there is some discussion in the derby developper list to increase maximum length
of most identifiers to 128. If that happens, these metadata functions will need to be updated
again. But for now, it these should return actual limits that are currently enforced.

-- 
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


Mime
View raw message