[DERBY-3270] Delayed (on-demand) creation of current user schema makes select from view belonging to other schema fail.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.3.1.4
• Fix Version/s: 10.5.1.1
• Component/s: SQL
• Assignee: Dag H. Wanvik
• Reporter: Dag H. Wanvik
• Created: 11/Dec/07 13:46
• Updated: 06/Mar/14 00:05
• Resolved: 16/Jan/09 18:57

Description

The enclosed repro fails with error 42Y07 'Schema BILL does not exist', even though
the query does not reference that schema; it selects from joe.myview.

Issue Links

• Is contained by: DERBY-6498 Derby does not always automatically create a user's schema
• is related to: DERBY-6361 Valid statements rejected if Derby has not implicitly created the current user's schema.
• relates to: DERBY-3945 Generation clauses which mention user-coded functions may produce different resuls depending on who performs the triggering INSERT/UPDATE