[
https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550450
]
Dag H. Wanvik commented on DERBY-3270:
--------------------------------------
A workaround is to make the referenced table in the view contain an explicit
schema prefix (joe.mytable)
in this case. Another workaround is to create a schema object for the user
referencing the view.
Note that the table name *is* eventually resolved correctly; a similar table,
bill.mytable in the repro,
is not chosen, even if the view reference does not have an explicit schema in
the table reference.
> 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
> Priority: Minor
> Attachments: 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.
