Opened 13 years ago
Closed 13 years ago
#3959 closed defect (invalid)
missing last right parenthesis, when "using unique"
Reported by: | Pena | Owned by: | pramsey |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | PostGIS Interface | Version: | 5.6 |
Severity: | minor | Keywords: | |
Cc: | kuken@… |
Description
Query is: location from ( select h.location, h.oid, k.expla, h.date1, h.expla, h.total, ku.locationname as name from (select pa.location, ha.type_id as oid, ha.date1, pa_n.name,
pa_n.location_id, ha.car_id, ha.total from pa join ha on ha.ha_pa_id = pa.pa_id left join pa_n on pa.pa_id = pa_n.pa_id where
ha.type_id = 121557 and status='11' and ha.is_valid is NULL
) as h
left join ku on h.ku_id=ku.ku_id left join k on h.type_id = k.type_id
where
k.code='sc' and syno=false and
(h.ku_id = 'AAC')
) as foobar
If Using unique is missing, then it seems, that last rigth parenthesis is missing - syntax error in mapserver log with debug 5
When the last line is "as foobar using unique oid" it works ok.
First has worked with 5.4.2 ok, but with 5.6.6 I get this problem. Lastone is working ok with both versions 5.4.2 and 5.6.6
Change History (2)
comment:1 by , 13 years ago
Component: | MapServer C Library → PostGIS Interface |
---|---|
Owner: | changed from | to
comment:2 by , 13 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
As the error message says:
msPostGISParseData(): Query error. Error parsing PostGIS DATA variable. You must specifiy 'using unique' when supplying a subselect in the data definition.
Paul: Any chance you can verify the bug? I can update...
Steve