Get with Include fails with multiple related entities

I’m having trouble getting your example code to work from the wiki under the ‘Joins’ section. I’ve created the relevant database objects, etc. I have a single workstation that has multiple employee’s. However, when executing the following code:

con.Get(new Workstation {WorkstationId = workStationId },
                    statement => statement.Include<Employee>()));

An exception is thrown:

Sequence contains more than one element

Stack trace if useful:

   at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source)
   at Dapper.FastCrud.SqlStatements.RelationshipSqlStatements`1.SelectById(IDbConnection connection, TEntity keyEntity, AggregatedSqlStatementOptions`1 statementOptions)
   at DapperCore.Repository.Repository.GetWorkstation(Int32 workStationId) in C:\W\DapperCore\DapperCore\src\DapperCore\Repository\Repository.cs:line 28
   at DapperConsole.Program.Main(String[] args) in C:\W\DapperCore\DapperCore\src\DapperConsole\Program.cs:line 23

It doesn’t seem to be able to handle the fact that the Workstation has many Employee objects associated with it.

If I remove the Employee’s from the database so that there is only a one-to-one relationship between the two. The code above works fine and I get only a single Employeeobject in the collection.

[MoonStorm]

I believe I found the problem. The algorithm is creating unique entities but this information should also be used later on as Dapper still returns an entity per row. The fix should be trivial and it will be faster than simply applying Distinct.

[MoonStorm]

Fixed and released. Give it a shot but be aware that Dapper is suffering from a bug that causes the async methods to fail.