[
https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650370#action_12650370
]
Dag H. Wanvik commented on DERBY-3270:
--------------------------------------
Hi Kathey,
I did run the regression successfully. The intention is that the view's
compilation schema only be used
when binding the part of the query tree that represents a view expansion. I
guess query transformations/optimizations could come into play and blur the
limits of what is what in the tree, but I would have thought that only happened
after binding time. When you say other contexts,
I am not sure what you are referring to, but I would also appreciate if someone
who knows this
code better could have a look at it, I freely admit I can't overview all the
possible consequences here. Note that Rick did something similar for computed
column computation, cf. DERBY-3945.
I'll upload a revision to fix the typos.
> 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-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.
