Well the hint makes perfect sense … assume there are no duplicates unless that
"hint" is there to advise you that:
a) there are duplicates
b) how to handle them
As for how to handle them - the query pulls back a feature with the same "id" …
that happen to differ based on the contents of a join.
Hi all,
Recently a client of ours forwarded along an initial patch that added
support for a query hint to do "distinct" queries. In this context
"distinct" implies the same semantics as the "distinct" keyword as
supported by most relational databases. The end use case of which is to
make GeoServer