You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2007/12/11 14:47:43 UTC
[jira] Created: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
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 <name> does not exist'.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3270:
---------------------------------
Attachment: derby-3270-dhw-2.stat
derby-3270-dhw-2.diff
Uploaded dhw-2 patch fixing typos, eol whitespace and long lines.
> 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-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.
[jira] Assigned: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden reassigned DERBY-3270:
-------------------------------------
Assignee: Kathey Marsden
> 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: 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.
[jira] Updated: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-3270:
----------------------------------
Derby Info: [Patch Available]
> 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.
[jira] Updated: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3270:
---------------------------------
Attachment: (was: derby-3270-dhw.stat)
> 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.
[jira] Updated: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3270:
---------------------------------
Derby Info: [Patch Available]
> 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: 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.
[jira] Commented: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650612#action_12650612 ]
Bryan Pendleton commented on DERBY-3270:
----------------------------------------
Assuming all the tests pass, I think Dag's suggested fix sounds promising.
In the code itself, the terms "origCompilationSchema" and "currCompilationSchema"
seem perhaps too generic. It would be interesting to consider whether the
code is any more self-evident if we used the terms "statementCompilationSchema"
and "expandedViewCompilationSchema" or something like that. Perhaps that
aids in comprehension, or perhaps it just crufts up the code even more.
Views, triggers, procedures, constraints and other "deferred" compilation
objects in the language seem to be thorny. They involve little snippets of SQL which
are parsed and compiled at awkward times in processing, and the rules for
how to interpret the ambiguities that arise are complex. It would be nice if we
can figure out ways to treat these various cases in common, so as Dag observed
mimic'ing what we do for generated columns in view processing seems on the
face of it appealing.
> 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-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.
[jira] Issue Comment Edited: (DERBY-3270) Delayed (on-demand)
creation of current user schema makes select from view belonging to other
schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649846#action_12649846 ]
dagw edited comment on DERBY-3270 at 11/21/08 3:24 PM:
----------------------------------------------------------------
Here is a patch suggestion (derby-3270-dhw) that makes ViewsTest and the lang suite run ok. Haven't run all regressions yet. Could this be a reasonable solution? It basically takes note of the
compilation schema of the view when it is being expanded and sets it as current compilation schema when expressions in the subquery are being bound, too..
was (Author: dagw):
Here is a patch suggestion (derby-3270-dhw) that makes ViewsTest and the lang suite run ok. Haven't run all regressions yet. Could this be a reasonable solution? It basically takes note of the
compilation schema of the view when it is being expanded and sets it as current compilation schema expressions are being bound, too..
> 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.
[jira] Resolved: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik resolved DERBY-3270.
----------------------------------
Resolution: Fixed
Fix Version/s: 10.5.0.0
Derby Info: (was: [Patch Available])
Resolving committed patch derby-3270-dhw-3 as svn 735084.
Not closing until we decide whether this should be backported.
> 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
> Fix For: 10.5.0.0
>
> Attachments: derby-3270-dhw-2.diff, derby-3270-dhw-2.stat, derby-3270-dhw-3.diff, derby-3270-dhw-3.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.
[jira] Updated: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3270:
---------------------------------
Attachment: Main.java
> 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.
[jira] Updated: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3270:
---------------------------------
Attachment: (was: Main.java)
> 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
>
> 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.
[jira] Updated: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3270:
---------------------------------
Attachment: derby-3270-dhw.stat
derby-3270-dhw.diff
Here is a patch suggestion (derby-3270-dhw) that makes ViewsTest and the lang suite run ok. Haven't run all regressions yet. Could this be a reasonable solution? It basically takes note of the
compilation schema of the view when it is being expanded and sets it as current compilation schema expressions are being bound, too..
> 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.
[jira] Updated: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3270:
---------------------------------
Description:
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.
was:
The enclosed repro fails with error 42Y07 'Schema <name> does not exist'.
> 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.
[jira] Commented: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647079#action_12647079 ]
Kathey Marsden commented on DERBY-3270:
---------------------------------------
Here is the full stack trace.
java.sql.SQLException: Schema 'BILL' does not exist
java.sql.SQLException: Schema 'BILL' does not exist
at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:45)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Util.java:201)
at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(TransactionResourceImpl.java:391)
at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(TransactionResourceImpl.java:346)
at org.apache.derby.impl.jdbc.EmbedConnection.handleException(EmbedConnection.java:2201)
at org.apache.derby.impl.jdbc.ConnectionChild.handleException(ConnectionChild.java:81)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:614)
at org.apache.derby.impl.jdbc.EmbedStatement.executeQuery(EmbedStatement.java:152)
at Main.doSingleDriver(Main.java:55)
at Main.main(Main.java:71)
Caused by: ERROR 42Y07: Schema 'BILL' does not exist
at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:286)
at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.getSchemaDescriptor(DataDictionaryImpl.java:1487)
at org.apache.derby.impl.sql.compile.QueryTreeNode.getSchemaDescriptor(QueryTreeNode.java:1343)
at org.apache.derby.impl.sql.compile.QueryTreeNode.getSchemaDescriptor(QueryTreeNode.java:1276)
at org.apache.derby.impl.sql.compile.TableName.bind(TableName.java:238)
at org.apache.derby.impl.sql.compile.FromBaseTable.getMatchingColumn(FromBaseTable.java:2524)
at org.apache.derby.impl.sql.compile.FromList.bindColumnReference(FromList.java:602)
at org.apache.derby.impl.sql.compile.ColumnReference.bindExpression(ColumnReference.java:349)
at org.apache.derby.impl.sql.compile.ResultColumn.bindExpression(ResultColumn.java:588)
at org.apache.derby.impl.sql.compile.ResultColumnList.bindExpressions(ResultColumnList.java:696)
at org.apache.derby.impl.sql.compile.SelectNode.bindExpressions(SelectNode.java:443)
at org.apache.derby.impl.sql.compile.FromSubquery.bindExpressions(FromSubquery.java:216)
at org.apache.derby.impl.sql.compile.FromList.bindExpressions(FromList.java:350)
at org.apache.derby.impl.sql.compile.SelectNode.bindExpressions(SelectNode.java:427)
at org.apache.derby.impl.sql.compile.DMLStatementNode.bindExpressions(DMLStatementNode.java:227)
at org.apache.derby.impl.sql.compile.DMLStatementNode.bind(DMLStatementNode.java:140)
at org.apache.derby.impl.sql.compile.CursorNode.bindStatement(CursorNode.java:236)
at org.apache.derby.impl.sql.GenericStatement.prepMinion(GenericStatement.java:314)
at org.apache.derby.impl.sql.GenericStatement.prepare(GenericStatement.java:88)
at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(GenericLanguageConne
ctionContext.java:796)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:606)
... 3 more
> 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.
[jira] Updated: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-3270:
----------------------------------
Attachment: derby-3270_diff.txt
Attached is my first attempt at a fix for this issue. The fix changes TableName.bind() to call the getSchemaDescriptor call that does not throw an exception instead of the one that does and to set the schemaName to null if it gets a null SchemaDescriptor back. The patch also adds a test for this issue.
The patch has the virtues of 1) fixing the issue and 2) passing regression tests.
I am not really sure that this is the right fix though. I don't understand why we are trying to bind to schema "bill" at all when the select is directly from the joe schema. The query in the end with this fix does indeed select from the joe schema, but why the intermediate step of binding to bill I don't know. I'd appreciate any input on the issue and the patch.
> 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.
[jira] Commented: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3270:
---------------------------------
Attachment: (was: derby-3270-dhw-3.diff)
> 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-3.diff, derby-3270-dhw-3.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.
[jira] Updated: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3270:
---------------------------------
Attachment: derby-3270-dhw.stat
derby-3270-dhw.diff
Re-attaching the patch; removing a superfluous diff from my experimenting.
> 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.
[jira] Commented: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663011#action_12663011 ]
Dag H. Wanvik commented on DERBY-3270:
--------------------------------------
Thanks, Rick.
I intend to commit this in a couple of days if there are no further comments.
> 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-3.diff, derby-3270-dhw-3.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.
[jira] Commented: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-3270:
----------------------------------
Derby Info: (was: [Patch Available])
Unchecking patch available while I try a new approach. Thanks Dag and Rick for the comments. I will try to digest them and come up with something better.
> 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.
[jira] Updated: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3270:
---------------------------------
Attachment: derby-3270-dhw-3.stat
derby-3270-dhw-3.diff
> 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-3.diff, derby-3270-dhw-3.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.
[jira] Updated: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3270:
---------------------------------
Attachment: derby-3270-dhw-3.diff
derby-3270-dhw-3.diff
Uploading a new version of this patch, derby-3270-dhw-3, which
introduces new push/pop methods to the compiler context to save the
default compilation schema when it needs to be temporarily changed. I
have made use of this in all the three places where this is currently
done, so as to hopefully make it easier to maintain this pattern.
Re-running regressions.
> 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-3.diff, derby-3270-dhw-3.diff, 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.
[jira] Commented: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649431#action_12649431 ]
Dag H. Wanvik commented on DERBY-3270:
--------------------------------------
What seems to be the problem is the following. The column reference
(A; expanded from *) is attempted bound against the table MYTABLE
twice inside FromBaseTable#getMatchingColumn:
First, when the view is created. At this time the current compilation
schema is JOE and there is no problem.
Second, the SELECT is bound, the view is expanded to a subquery (under
DMLStatementNode#bind's call to bindTables->bindNonVTITables, parsed
and table reference bound using the original schema, see comment in
that method), and then later the expressions are bound under
DMLStatementNode#bind's call to bindExpressions. This time the
compilation schema is reset to BILL, however.
In FromBaseTable#getMatchingColumn, the call:
columnsTableName.bind(this.getDataDictionary());
tries to bind the unqualified table name (MYTABLE) and finds the current schema
BILL. If BILL already exists, this goes well, if not, we see
DERBY-3270. Now, if this is bound incorrectly, why does it work? It
seems this binding is inconsequential, in that columnsTableName is a
local variable, and if we follow the logic in getMatchingColumn after
the binding, we see that the matching happens with this call:
if (columnsTableName == null || columnsTableName.equals(exposedTableName))
{
resultColumn = resultColumns.getResultColumn(columnReference.getColumnName());
exposedTableName has the same (wrong) binding, derived from
FromTable#origTableName, so the equals test works. Next, we basically
just checks if "A" is present in resultColumns. resultColumns is
correct since the table was bound correctly already.
I am not sure what the right fix is here, though. It would appear that
binding schema incorrectly as done in getMatchingColumn (and for origTableName)
is not good, and the first patch doesn't address that.
Maybe we could note the original compilation schema in the root of the view subquery
subsituted from the view name in the original query and find that
(walking up the tree) when the current default schema is looked up
somehow?
> 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.
[jira] Commented: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3270:
---------------------------------
Attachment: (was: derby-3270-dhw.diff)
> 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.
[jira] Assigned: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik reassigned DERBY-3270:
------------------------------------
Assignee: Dag H. Wanvik
> 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.
[jira] Commented: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661659#action_12661659 ]
Rick Hillegas commented on DERBY-3270:
--------------------------------------
Thanks, Dag. Factoring out this common logic seems like a great idea to me.
> 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-3.diff, derby-3270-dhw-3.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.
[jira] Commented: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3270:
---------------------------------
Attachment: Main.java
> 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 <name> does not exist'.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DERBY-3270) Delayed (on-demand) creation of
current user schema makes select from view belonging to other schema fail.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden reassigned DERBY-3270:
-------------------------------------
Assignee: (was: Kathey Marsden)
Unassigning myself from this issue. Looks like Dag has a promising patch and I am out for a while and don't want to hold up progress.
> 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: 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.