Opened 17 years ago
Closed 16 years ago
#341 closed defect (fixed)
PostGIS defect : SelectAggregate does not support DISTINCT
| Reported by: | bscott | Owned by: | |
|---|---|---|---|
| Priority: | critical | Milestone: | 3.4.0 |
| Component: | PostGIS Provider | Version: | 3.2.0 |
| Severity: | 1 | Keywords: | |
| Cc: | External ID: |
Description
Even if the SelectAggregatesCommand::SetDistinct function is called with true The distinct clause is not appended to the internal sql query.
Change History (7)
follow-up: 2 comment:1 by , 17 years ago
| Status: | new → assigned |
|---|
comment:2 by , 17 years ago
Mateusz i've just submit on nabble.fdo.internal a little patch to fix it. It was quite a simple one
comment:4 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:5 by , 16 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
comment:6 by , 16 years ago
| Owner: | removed |
|---|---|
| Status: | reopened → new |
comment:7 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Bruno,
Yes, I confirm that SetDistinct call has no effect. Simply, a value being set is not used anywhere in the command implementation. Means, not yet supported. I will try to work on it soon but I can't promise it happens before the weekend.