db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3270) Delayed (on-demand) creation of current user schema makes select from view belonging to other schema fail.
Date Fri, 28 Nov 2008 22:02:44 GMT

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

Dag H. Wanvik commented on DERBY-3270:
--------------------------------------

I plan to see if there is a way to share logic for the cases where we temporarily set the
current schema
back; at a minimum to make naming uniform. I'll be out the next two week, so feel free
to grab this issue.


> Delayed (on-demand) creation of current user schema makes select from view belonging
to other schema fail.
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3270
>                 URL: https://issues.apache.org/jira/browse/DERBY-3270
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.3.1.4
>            Reporter: Dag H. Wanvik
>            Assignee: Dag H. Wanvik
>            Priority: Minor
>         Attachments: derby-3270-dhw-2.diff, derby-3270-dhw-2.stat, derby-3270-dhw.diff,
derby-3270-dhw.stat, derby-3270_diff.txt, Main.java
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message