[
https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650284#action_12650284
]
Kathey Marsden commented on DERBY-3270:
---------------------------------------
Thanks Dag for the patch! I noticed a couple small typos in the comments
* If this subquery represents and expanded view, we need this to bind
I think it should be "an" instead of "and"
* being froma view.
"from" and "a" should be separate words.
As for the patch itself, I am not sure I understand the impact of changing the
compilation schema in other contexts. It would be good if someone else more
familiar with this code could review. Would you like me to run tests with the
patch? I'd be happy to do so.
> 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.
