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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2011/03/19 04:45:29 UTC
[jira] Commented: (DERBY-5005) Error when fully qualifying a field
from a view in an ORDER BY clause
[ https://issues.apache.org/jira/browse/DERBY-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008725#comment-13008725 ]
Kathey Marsden commented on DERBY-5005:
---------------------------------------
Running Suites.All the 10.5 patch I see this failure. I don't think it is related to the change and don't immediately see an issue filed but will take a closer look
1) SecureServerTest( Opened = false, Authenticated= true, CustomDerbyProperties=
null, WildCardHost= 0.00.000.0 )junit.framework.AssertionFailedError: SecureSer
verTest( Opened = false, Authenticated= true, CustomDerbyProperties= null, WildC
ardHost= 0.00.000.0 )
Expected: Security manager installed using the Basic server security policy.
But saw:
at org.apache.derbyTesting.functionTests.tests.derbynet.SecureServerTest
.testServerStartup(SecureServerTest.java:345)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:37)
at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:
109)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57
)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
FAILURES!!!
Tests run: 11318, Failures: 1, Errors: 1
jvm is:
$ java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pwi3260sr9-20101125_01(SR9))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-201011
24_69295 (JIT enabled, AOT enabled)
J9VM - 20101124_069295
JIT - r9_20101028_17488ifx2
GC - 20101027_AA)
JCL - 20101119_01
> Error when fully qualifying a field from a view in an ORDER BY clause
> ---------------------------------------------------------------------
>
> Key: DERBY-5005
> URL: https://issues.apache.org/jira/browse/DERBY-5005
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1, 10.3.3.0, 10.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, 10.6.1.0, 10.6.2.1, 10.7.1.1
> Environment: Windows 7
> Reporter: Lukas Eder
> Assignee: Dag H. Wanvik
> Priority: Minor
> Labels: order, sql, syntax, views
> Fix For: 10.8.0.0
>
> Attachments: 5005.sql, derby-5005.diff, derby-5005.stat, derby-5005_10_5_diff.txt, derby-5005b.diff, derby-5005b.stat
>
>
> I have a strange issue that can be reproduced easily with the following objects in schema "test":
> create table a (a integer);
> insert into a (a) values(1);
> create view v as select * from a;
> This works:
> select test.a.a from test.a where test.a.a <> 2 order by test.a.a asc;
> This doesn't work:
> select test.v.a from test.v where test.v.a <> 2 order by test.v.a asc;
> But this does:
> select test.v.a from test.v where test.v.a <> 2 order by v.a asc;
> This is the error I get:
> Error: 'TEST.V' is not an exposed table name in the scope in which it appears.
> SQLState: 42X10
> ErrorCode: -1
> I've tried quite a few SELECT clauses, and I think the ORDER BY clause is the only one having this issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira