Unexpected DISTINCT?

DAWG,

   I have an implementation question for which I cannot find an  
answer in the spec.

   Given a SELECT query for which some results are duplicated, and  
which does not specify DISTINCT, is it acceptable for an  
implementation to return DISTINCT (or partially DISTINCT) results?

   This is exercised by <http://www.w3.org/2001/sw/DataAccess/tests/ 
#modifer-limit>:

- with no DISTINCT processing, the results are [ 1, 1 ].
- with DISTINCT processing, the results are [ 1, 2 ].

   I seem to recall from informal sources that this is acceptable,  
but it would be good to get a firm documented answer, particularly  
when I can see that this could be contentious.

   Thanks,

-R

Received on Sunday, 25 February 2007 17:58:14 UTC