#28 DISTINCT mandatory

[John Goerzen]

There appears to be no way to turn off DISTINCT in the
SELECT query. I don't know why this is the default (it
seriously hinders performace on many backends), and
being unable to disable it renders haskelldb unusable
for various purposes (esp. for tables that hold event
logs and the like)

[Bjorn Bringert]

Logged In: YES
user_id=123762

The reason for this is that HaskellDB is based on relational
algebra, where results are sets, i.e. contain no duplicates.
This might not always be what the user wants, so there ought
to be a way to allow duplicate records. The only workarounds
at the moment are to include some unique value in each
record (such as the record key, or possible a date & time
for things like events), or to use an aggregate query with a
count field, which at least gives most of the same information.

I guess it should be possible to add a new query operator,
which causes duplicate results to be returned, or to allow
this in some other way. Anyone care to submit a patch?