Issue Details (XML | Word | Printable)

Key: DERBY-104
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Bernt M. Johnsen
Reporter: Bernd Ruehlicke
Votes: 3
Watchers: 4
Operations

If you were logged in you would be able to see more operations.
Derby

Get rid of the Max lenght of 18 for constraint names

Created: 16/Dec/04 10:28 PM   Updated: 01/Jul/09 12:40 AM
Return to search
Component/s: SQL
Affects Version/s: 10.0.2.0, 10.0.2.1, 10.0.2.2, 10.1.1.0
Fix Version/s: 10.1.1.0

Time Tracking:
Issue & Sub-Tasks
Issue Only
Not Specified

File Attachments:
  Size
Text File Licensed for inclusion in ASF works derby-id-plus-renames-v2.patch 2004-12-17 12:39 PM Philipp Hug 93 kB

Resolution Date: 18/Jun/05 07:20 AM

Sub-Tasks  All   Open   
No sub-tasks match this view.

 Description  « Hide
If not unlimited than we should at least make them 80 (just to pick a abitrary number)

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Philipp Hug added a comment - 17/Dec/04 12:39 PM
This patch extends all maximum identifier names to 128.
It also renames the DB2Limit.java into DerbyLimit.java the constants it contains from DB2_ to DERBY_

Bernd Ruehlicke added a comment - 17/Dec/04 03:05 PM
Cool ! When will the next official jar drop be of Derby which includes this ?

Any document how to incorporate this patch into the source ?

Thanx again
B-)

Daniel John Debrunner added a comment - 17/Dec/04 03:12 PM
Note that the this specific patch (derby-id-plus-renames-v2.patch) has a veto against it.

http://nagoya.apache.org/eyebrowse/ReadMsg?listName=derby-dev@db.apache.org&msgNo=1385

See the thread for more details.

Geoff Soutter added a comment - 11/Jan/05 10:08 PM
I'd like to see this one fixed as well.

I have built a hacked local version with just the sqlgrammer.jj file modified to use the 128 char lengths rather than 18 char lengths, which is easy to do and seems to work.

Geoff Soutter added a comment - 11/Jan/05 10:44 PM
A couple of notes:

- we probably shouldn't rename DB2_ limits until the values have been changed to Derby specific values - otherwise it makes it even harder to figure out where the value came from.

- changing some of these limits may make the DatabaseMetadata provided by the IBM DB2 JDBC Driver incorrect when used in server mode (embedded mode is OK). Not sure what we can do about that considering we don't have the source.

Bernt M. Johnsen added a comment - 04/May/05 07:04 PM
What I want to do:
1) Change the name of DB2Limit.java to Limits.java
2) Ensure that all DB2 related constants are prefixed by DB2_
   There are now 6 constants which do not have the prefix: MIN_COL_LENGTH_FOR_CURRENT_USER
   MIN_COL_LENGTH_FOR_CURRENT_SCHEMA, MAX_USERID_LENGTH, MAX_DECIMAL_PRECISION_SCALE,
   DEFAULT_DECIMAL_PRECISION, DEFAULT_DECIMAL_SCALE
   These should get the DB2_ prefix if they are DB2-related (are they?)
3) DB2_MAX_IDENTIFIER_LENGTH18/30/128 changes to MAX_IDENITIFER_LENGTH which is set to 128
4) extend lang/indentifier.sql with positive and negative tests for more identifiers
   than table name (constraint, cursor, function, index, trigger, column, schema,
   savepoint and view names)

Bernt M. Johnsen added a comment - 06/May/05 06:59 PM
There seems to be no (practical) limit on cursor names:
 get cursor zzzz as 'select * from tab';
where zzzz is 10000 characters long works prefectly in ij (same goes for next etc).

Satheesh Bandaram added a comment - 02/Jun/05 06:20 AM
Fix merged into trunk. Closing it.

Andrew McIntyre added a comment - 18/Jun/05 07:14 AM
reopening to set Affects and Fix In.