v10.2.0

This release sends less data over the wire and fixes three ways a save could lose data.

• Some queries made the database return every matching row so the client could pick the answer. First after a Select that builds an object read 494 rows in 10.1.1 to return one, and reads one now (#116, #172).
• Three ways a save could overwrite another user's change without an error, or report success and write nothing, are fixed (#115, #109).
• The server can roll back an idle transaction and refuse a transaction token another caller opened. Both are off until you turn them on (#54).
• On MongoDB, Cosmos DB and similar databases, the server can stop a save from erasing the parts of a document it did not mention (#103).
• A few queries that EF Core refuses used to return an answer here. They now throw EF Core's own exception. Read the list before you upgrade (#178, #149, #152, #141, #148).
• Verified against Microsoft's EF Core specification suite: 29958 tests, none failing. Every relational test also ran against plain EF Core (#167).

dotnet add package InfoCarrier.Core              # the client and the server
dotnet add package InfoCarrier.Core.AspNetCore   # the server endpoint

• What is new in 10.2, the full list
• Limitations, worth reading before you adopt
• Documentation