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

["Myrna van Lunteren (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-6498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921682#comment-13921682 ] 

Myrna van Lunteren commented on DERBY-6498:
-------------------------------------------

In DERBY-6361 Rick said we needed:
" a generic issue [...] to avoid filing a new issue for each instance of this problem. I regard it as a systemic problem which ultimately needs a systemic solution."

> Derby does not always automatically create a user's schema
> ----------------------------------------------------------
>
>                 Key: DERBY-6498
>                 URL: https://issues.apache.org/jira/browse/DERBY-6498
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.10.1.1
>            Reporter: Myrna van Lunteren
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)