Issue 67008 - creating a query based on another query with non-unique column names fails
Summary: creating a query based on another query with non-unique column names fails
Status: ACCEPTED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: recent-trunk
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-04 14:06 UTC by Frank Schönheit
Modified: 2017-05-20 10:48 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
document to reproduce the bug case (10.95 KB, application/vnd.sun.xml.base)
2006-07-04 14:10 UTC, Frank Schönheit 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Frank Schönheit 2006-07-04 14:06:19 UTC 
This bug exists in the implementation of "Queries in Queries", filed as issue
51143. It can be reproduced in the master builds as soon as CWS qiq
(http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Fqiq) is
integrated.
- open the attached database document
- with the query wizard, create a query based on the query "non-unique column
  names", adding all fields
- open the resulting query
=> error message saying that the data content could not be loaded.

The problem here is that the existing query selects column "Name" twice. When
executed directly, OOo makes the names unique, by naming on of them "Name1"
instead. The query wizard uses this "Name1" column name. Now when the query is
used as sub query, the names are kept non-unique, so the reference to "Name1" in
the wizard-generated query is bogus.
Comment 1 Frank Schönheit 2006-07-04 14:08:11 UTC 
accepting
Comment 2 Frank Schönheit 2006-07-04 14:10:20 UTC 
Created attachment 37495 [details]
document to reproduce the bug case
Comment 3 Frank Schönheit 2006-08-07 10:54:45 UTC 
hard to fix, and IMO not important enough for 2.x - the valid and easy
workaround is to give an alias name to the second column when designing the query.
Comment 4 Marcus 2017-05-20 10:48:18 UTC 
Reset assigne to the default "issues@openoffice.apache.org".