Opened 16 years ago
Closed 16 years ago
#614 closed defect (fixed)
Selection against a joined feature source returns an extra feature
Reported by: | mgluobin | Owned by: | brucedechant |
---|---|---|---|
Priority: | high | Milestone: | 2.1 |
Component: | General | Version: | 2.0.1 |
Severity: | blocker | Keywords: | |
Cc: | brucedechant | External ID: |
Description
Compiling the source code from SVN trunk vesion, when doing selection against a joined feature source the 1st feature is always returned regardless of filter along with the expected results.
Change History (11)
comment:1 by , 16 years ago
Component: | General → Server |
---|---|
Severity: | trivial → blocker |
comment:2 by , 16 years ago
Component: | Server → General |
---|
comment:3 by , 16 years ago
Cc: | added |
---|
follow-up: 5 comment:4 by , 16 years ago
What feature sources are you joining? What is the primary and what is the secondary? (Example: Primary=SDF Secondary=Access)
What kind of join are you doing? Inner? Outer? 1-1? 1-Many?
What does your filter look like that exhibts this issue?
comment:5 by , 16 years ago
When i use the task of query in the ajaxviewer, the query result exhibts this issue. And only the attribute data of the 1st feature in query result can be listed in the attribute panel,the others can not be listed.
I use the data:
Primary=Shp Secondary= Access or mysql <RelateType>LeftOuter</RelateType> <ForceOneToOne>false</ForceOneToOne>
comment:6 by , 16 years ago
I cannot reproduce this with a SHP to Access join using the current trunk code. (My dataset was just sample world countries)
I used the following filter on the layer: (Key is from the primary feature source) Key >= 'CA'
It only returned Macedonia and nothing else when I entered "AC" into the query.
Can you provide the filter you are using that causes this issue?
follow-up: 8 comment:7 by , 16 years ago
I need to clarify that the query I specify for the search task is: Name LIKE '%$USER_VARIABLE%'
Which is a different attribute then what the layer filter uses.
comment:8 by , 16 years ago
comment:11 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
See submission revision 3524.
using a server trunk build (3247) on windows xp, when doing querying against a joined feature in ajaxviewer , the 1st feature is always returned regardless of filter along with the expected results.