You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Satheesh Bandaram (JIRA)" <de...@db.apache.org> on 2004/10/26 21:11:43 UTC
[jira] Created: (DERBY-50) getMaxColumnNameLength() database metadata function returns incorrect value.
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
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
Re: [jira] Created: (DERBY-50) getMaxColumnNameLength() database
metadata function returns incorrect value.
Posted by Satheesh Bandaram <sa...@Sourcery.Org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have submitted a fix for this problem...
Satheesh
Satheesh Bandaram (JIRA) wrote:
>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
>
>
>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.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBfqD8ENVNIY6DZ7ERAjKqAJ434UnZdinWr7kuRsOMB/h2GCp9oACfUmd6
NNJHCLEPUHu/iSsZTM49OCw=
=3Q3l
-----END PGP SIGNATURE-----
[jira] Commented: (DERBY-50) getMaxColumnNameLength() database metadata function returns incorrect value.
Posted by "Shreyas Kaushik (JIRA)" <de...@db.apache.org>.
[ http://nagoya.apache.org/jira/browse/DERBY-50?page=comments#action_55666 ]
Shreyas Kaushik commented on DERBY-50:
--------------------------------------
It returned the correct value of 30. Has it been already fixed?
> getMaxColumnNameLength() database metadata function returns incorrect value.
> ----------------------------------------------------------------------------
>
> Key: DERBY-50
> URL: http://nagoya.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
>
> 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://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-50) getMaxColumnNameLength() database metadata function returns incorrect value.
Posted by "Satheesh Bandaram (JIRA)" <de...@db.apache.org>.
[ http://nagoya.apache.org/jira/browse/DERBY-50?page=history ]
Satheesh Bandaram resolved DERBY-50:
------------------------------------
Resolution: Fixed
Fix Version: 10.0.2.0
Checked in changes and submitted patch as 55630.
> getMaxColumnNameLength() database metadata function returns incorrect value.
> ----------------------------------------------------------------------------
>
> Key: DERBY-50
> URL: http://nagoya.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://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-50) getMaxColumnNameLength() database metadata function returns incorrect value.
Posted by "Satheesh Bandaram (JIRA)" <de...@db.apache.org>.
[ 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