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