Question: I'm using an ebean query in the play! framework to find a list of records based on a distinct column. It seems like a pretty simple query but the problem is the ebean method setDistinct(true) isn't actually setting the query to distinct.

My query is:

```
List<Song> allSongs = Song.find.select("artistName").setDistinct(true).findList();

```

In my results I get duplicate artist names.

From what I've seen I believe this is the correct syntax but I could be wrong. I'd appreciate any help. Thank you.

Answer: 
I just faced the same issue out of the blue and can not figure it out. As hfs said its been fixed in a later version but if you are stuck for a while you can use 

```
findSet()

```

So in your example use 

```
List<Song> allSongs = Song.find.select("artistName").setDistinct(true).findSet();

```
According to [issue #158: Add support for using setDistinct (by excluding id property from generated sql)](https://github.com/ebean-orm/avaje-ebeanorm/issues/158) on the Ebean bug tracker, the problem is that an ID column is added to the beginning of the select query implicitly. That makes the distinct keyword act on the ID column, which will always be distinct.

This is supposed to be fixed in Ebean 4.1.2.