[
https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649441#action_12649441
]
Rick Hillegas commented on DERBY-3270:
--------------------------------------
Thanks for this analysis, Dag. It seems to me that the problem could be fixed
if the second binding did not occur. Maybe the view substitution logic could
mark the subquery as "already bound" and this could short-circuit the later
re-binding. Haven't looked at the code and am just waving my hands here.
> 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: Kathey Marsden
> Priority: Minor
> Attachments: 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.
