db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2504) SQL warning "01501: The view V21VIEWTEST has been dropped" can be lost (ie. not seen when it should be)
Date Fri, 30 Mar 2007 00:54:25 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485392

Daniel John Debrunner commented on DERBY-2504:

This is because the ViewDescriptor.makeInvalid() is using the getLastActivation()  method
on LanguageConnectionContext.
At runtime there is no guarantee that the currently executing statement is the last activation.

I just noticed this because the getLastActivation() method caught my eye, I couldn't see any
valid reason for such a method, it should be removed as part of this bug fix.

> SQL warning "01501: The view V21VIEWTEST has been dropped"  can be lost (ie. not seen
when it should be)
> --------------------------------------------------------------------------------------------------------
>                 Key: DERBY-2504
>                 URL: https://issues.apache.org/jira/browse/DERBY-2504
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions:,,
>            Reporter: Daniel John Debrunner
>            Priority: Minor
> Example, grantRevokeDDL test has this SQL and correct output:
> revoke select on t11ViewTest from public;
> 0 rows inserted/updated/deleted
> WARNING 01501: The view V21VIEWTEST has been dropped.
> But if instead the statement is prepared and another statement prepared before the execution
then the warning will not appear
> prepare R1 as 'revoke select on t11ViewTest from public';
> ij(MAMTA1)> prepare V1 as 'values 1';
> ij(MAMTA1)> execute R1;
> 0 rows inserted/updated/deleted
> ij(MAMTA1)> execute V1;
> 1          
> -----------
> 1          
> 1 row selected
> If I don't prepare V1 then the exception is seen, so it's not the prepare causing the

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message