Collation conflict error of UpdateAsync operation using templates after update from 3.1.6 to 3.2.3

After updating from linqdb version 3.1.6 to 3.2.3 we have faced with a lot of exceptions when on UpdateAsync operation. Error:

System.Data.SqlClient.SqlException (0x80131904): Cannot resolve the collation conflict between "SQL_Latin1_General_CP1251_CI_AS" and "Cyrillic_General_CI_AS" in the equal to operation

Example update operation:

                var updateTempTable = await db.CreateTempTableAsync(
                    $"temp_{Guid.NewGuid()}_{nameof(Item)}",
                    itemsToUpdate, cancellationToken: ct);

                var recordsToUpdate =
                    from s in db.Items.With("NOLOCK")
                    from t in updateTempTable.InnerJoin(x =>
                        x.ItemId== s.ItemId)
                    select new {s, t};

                await recordsToUpdate
                    .Set(v => v.s.Name, v => v.t.Name)
                    .Set(v => v.s.DateUpdated, v => DateTimeOffset.Now)
                    .UpdateAsync(ct);

Example table definition:

    [Table(Schema="dbo", Name="Item")]
    public partial class Item
    {
        [PrimaryKey, NotNull] public int            ItemId      { get; set; }
        [Column,     NotNull] public string         Name        { get; set; }
        [Column,     NotNull] public DateTimeOffset DateUpdated { get; set; }
    }

Database collation SQL_Latin1_General_CP1251_CI_AS

When we downgrade from 3.2.3 to 3.1.6, then all works as before. What was changed? And how to adapt to a new logic? For all tables, which use as source for creating temp tables we should add creation format of columns? Like:

[Column(CreateFormat = "{0} {1} SQL_Latin1_General_CP1251_CI_AS {2} {3}"), Nullable]

---

.NET Core 3.1 linq2db version: 3.2.3 Database Server: MSSQL

[MaceWindu]

Another solution will be adding collation to each column in temp table mapping, so it will use explicit collation instead of tempdb collation.

[MaceWindu]

I see where the problem. In 3.2 we introduced support for real temporary tables, so CreateTemp table default behavior changed to create temporary table, which is created in tempdb. In your case tempdb collation differ from collation of your db, which results in collation conflicts.

You should update CreateTempTable call to use real table (pre-3.2 behavior)