[DERBY-5779] Table functions should only accept arguments which are constant in their query block.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.9.1.0
• Fix Version/s: 10.10.1.1
• Component/s: SQL
• Labels: derby_backport_reject_10_9
• Urgency: Normal
• Issue & fix info: Patch Available, Release Note Needed
• Bug behavior facts: Deviation from standard, Wrong query result
• Assignee: Richard N. Hillegas
• Reporter: Richard N. Hillegas
• Created: 23/May/12 13:55
• Updated: 02/Jun/14 12:37
• Resolved: 27/Jun/13 23:02

Description

Derby lets you invoke a table function in the FROM list of a query, passing in arguments built out of columns in other tables in the FROM list. This syntax is illegal and the resulting queries have no meaning under the SQL Standard. See the discussion on DERBY-5554. We should forbid this syntax. Similar syntax involving correlated subqueries in the FROM list is already forbidden. Fixing this will create a backward incompatibility which requires a release note.

Issue Links

• is related to: DERBY-6593 Using a natural join, you can invoke a table function with an argument which is outside the scope of the query block.
• relates to: DERBY-5554 NullPointerException in generated VTI code