[DERBY-6498] Derby does not always automatically create a user's schema

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.10.1.1
• Component/s: SQL
• Assignee: Unassigned
• Reporter: Myrna van Lunteren
• Created: 06/Mar/14 00:04
• Updated: 06/Mar/14 00:10

Description

There are many examples of statements failing because Derby has not implicitly created the schema associated with the current user. You don't see this if the schema is the default APP schema. But if the user is anyone other than APP, then various statements can fail. Maybe we should implicitly create a schema even if the user isn't APP. Right now, you get an error like this:

ERROR 42Y07: Schema 'ROOT' does not exist

This is intended as a master issue, to link various other issues that have been fixed, or further issues as they are found/reported.

Issue Links

• contains: DERBY-5139 User schema not auto-created on creation of self-referencing table
• contains: DERBY-3945 Generation clauses which mention user-coded functions may produce different resuls depending on who performs the triggering INSERT/UPDATE
• contains: DERBY-6361 Valid statements rejected if Derby has not implicitly created the current user's schema.
• contains: DERBY-3270 Delayed (on-demand) creation of current user schema makes select from view belonging to other schema fail.