db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3270) Delayed (on-demand) creation of current user schema makes select from view belonging to other schema fail.
Date Tue, 18 Nov 2008 22:15:44 GMT

     [ 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.


Mime
View raw message