[DERBY-3945] Generation clauses which mention user-coded functions may produce different resuls depending on who performs the triggering INSERT/UPDATE

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.5.1.1
• Fix Version/s: 10.5.1.1
• Component/s: SQL
• Issue & fix info: Patch Available
• Assignee: Richard N. Hillegas
• Reporter: Richard N. Hillegas
• Created: 11/Nov/08 20:44
• Updated: 06/Mar/14 00:05
• Resolved: 20/Nov/08 17:05

Description

This is similar to DERBY-3944. The compiler uses the current schema in order to resolve unqualifed function names when preparing INSERT/UPDATE statement. This means that a generation clause may evaluate differently depending on who invokes the triggering INSERT/UPDATE statement. This violates the requirement that generation clause should be deterministic (see part 2 of the ANSI/ISO standard, section 4.16.

Hopefully, the same patch will fix both DERBY-3944 and this issue.

Issue Links

• Is contained by: DERBY-6498 Derby does not always automatically create a user's schema
• is part of: DERBY-481 implement SQL generated columns
• is related to: DERBY-3944 CHECK constraints involving user-coded functions may return different results depending on who performs the triggering INSERT/UPDATE
• is related to: DERBY-6361 Valid statements rejected if Derby has not implicitly created the current user's schema.
• is related to: DERBY-3270 Delayed (on-demand) creation of current user schema makes select from view belonging to other schema fail.