[ https://issues.apache.org/jira/browse/DERBY-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lukas Eder closed DERBY-5005. ----------------------------- > 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.5.3.2, 10.6.2.3, 10.7.1.4, 10.8.1.2 > > 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