db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Satheesh Bandaram <sathe...@Sourcery.Org>
Subject Re: Identifier Limitations - once again
Date Mon, 13 Dec 2004 07:59:01 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
There is metadata API to retrieve maximum lengths allowed (like the one
you mentioned, getMaxColumnNameLength), but there is no way to set the
maximum length. I do agree that maximum length of 18 for a cursor name
or constraint name or index name is pretty restrictive.

Satheesh

Philipp Hug wrote:

> I know this has been discussed before, but there hasn't been a consus
if those limitations should be extended...
> At the moment, I patched Derby to allow longer identifier for
index/constraint names, because the CMP engine I'm using, uses
getMaxColumnNameLength() as limitation for index name.
> Does anyone know of any metadata attribute that would specify the
maximum allowed length for an index/constraint name? If there is such an
attribute, I could live with that and would just fix the CMP engine?
Otherwise we should really think about extending it to a decent value
(e.g. 30 or 128).
>
> btw: cloudscape 9 didn't have this limitation, it has been added in
cloudscape 10/derby
>
> greets
> philipp
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
 
iD8DBQFBvUvEENVNIY6DZ7ERApW1AJ9KMOobSeYfAb3dj4EriSxZqdEjkgCdHxjk
9rK3U3J+3KY9PJxGkF3PSBI=
=kDL8
-----END PGP SIGNATURE-----


Mime
View raw message