Activity

1. rbsdotnet

   changed the title [-]User AddBulkOperationSupport[/-] [+]Use AddBulkOperationSupport[/+] on Jul 18, 2026
2. PawelGerr

   added a commit that references this issue on Jul 18, 2026

   fix: prevent other conventions from overriding temp table and collect…

   ...

   5a01728
3. PawelGerr commented on Jul 18, 2026

   

   PawelGerr

   on Jul 18, 2026

   Owner

   More actions

   Thanks for the report!

   Cause: The error occurs when something in your model configuration renames all entity types, for example a naming-convention plugin or a loop over modelBuilder.Model.GetEntityTypes() that calls SetTableName(...)/ToTable(...). AddBulkOperationSupport registers internal entity types such as TempTable<DateOnly> and TempTable<DateOnly?>. A rename based on the CLR type name maps both of them to the same name (TempTable`1), and EF Core then fails model validation with the "no linking relationship" error you posted. The error message in your report contains TempTable`1, which is the CLR reflection name, so I assume you have such a rename in place.

   Fix: Released in 10.4.0-beta03. The internal registrations now use the data-annotation configuration source, so conventions (including naming-convention plugins) can no longer override their table names. Please update and try again.

   One caveat: If you rename tables explicitly in OnModelCreating, for example:

   foreach (var entityType in modelBuilder.Model.GetEntityTypes())
   {
      entityType.SetTableName(entityType.ClrType.Name);
   }

   then explicit configuration still wins by design and the error will remain. In that case, skip the internal entity types in your loop:

   foreach (var entityType in modelBuilder.Model.GetEntityTypes())
   {
      if (entityType.Name.StartsWith("Thinktecture:", StringComparison.Ordinal))
         continue;
   
      entityType.SetTableName(entityType.ClrType.Name);
   }

   If the beta does not resolve the problem for you, please provide a minimal repro.