[DERBY-3512] Using functions, you can create a LONG VARCHAR value which is longer than the maximum length of a Derby LONG VARCHAR

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.4.1.3
• Component/s: SQL
• Labels: derby_triage10_11
• Urgency: Normal
• Issue & fix info: High Value Fix, Repro attached
• Assignee: Unassigned
• Reporter: Richard N. Hillegas
• Created: 07/Mar/08 16:34
• Updated: 03/Jul/13 15:26

Description

I can create a static method which returns a long String and register this as a function which returns LONG VARCHAR. I am able to invoke this function and create a LONG VARCHAR value which is longer than the maximum length which Derby allows for this datatype (32700 characters).

It is not clear to me what is supposed to happen in this situation according to the SQL standard. However, the current behavior seems wrong. Here are two possible correct behaviors:

1) Raise an exception if the user-coded method violates the declared contract of the CREATE FUNCTION statement.

2) Silently truncate the value returned by the user-coded method.

There may be a similar problem with methods which return byte[] and which are registered as functions returning (LONG) VARCHAR FOR BIT DATA. However, experiments to test this are blocked by DERBY-3511.

I will attach a test case demonstrating the problem.

Issue Links

• blocks: DERBY-3511 Cannot resolve functions which return VARCHAR FOR BIT DATA or LONG VARCHAR FOR BIT DATA
• relates to: DERBY-3341 TABLE FUNCTION returning CHAR values does not return a correct value if the Java ResultSet class returns a value less than the length of the defined CHAR.