4.0.13.523 SD.LLBLGen.Pro.DQE.SqlServer.dll
4.0.13.0725 SD.LLBLGen.Pro.ORMSupportClasses.dll
4.0.13.406 SD.LLBLGen.Pro.ORMSupportClasses.Web.dll
DotNet 4.0 vs2010 project
Adapter template
SQL Server 2008 R2
I have a timing issue that I want to track down. A pair of tables that need to be fetched together both have a [DATETIME] column in the primary key.
This works fine as long as the datetimes used are not the same minute. i.e. if I wait a minute between each save, when I next fetch the collection it works. If I save twice in a minute it will only fetch one of the rows in the prefetch. So saving and fetching the top level enities are working as expected.
Somewhere this datetime is being rounded or used to the minute to see how to create the sql to get the rows needed in the prefetch path. So if there are two top level rows in the collection, each with different dates but at the same minute, the prefetch calculation thinks that only one row needs to be fetched in the prefetch.
To make things more confusing, the sql generated contains the full datetime down to the milliseconds.
Any ideas on what could be going wrong?