SQL, ulong, uint

 @markolbert Unsigned longs, ints, and shorts are not yet supported for SQL Server because the underlying ADO.NET provider for SQL Server ("a.k.a. SQL Client") does not support them. They can be used with other providers, such as SQLite. We plan to support them for SQL Server when type conversions are implemented. This is being tracked by issue #242. Closing this as a duplicate of that issue.

https://github.com/dotnet/efcore/issues/6480

These are the default conversions:

• sbyte -> smallint
• ushort -> int
• uint -> bigint
• ulong -> decimal(20, 0)
• char -> nchar(1)

These can be used by changing the store type:

• sbyte -> byte (not order preserving)
• ushort -> short (not order preserving)
• uint -> int (not order preserving)
• ulong -> long (not order preserving)
• char -> other string types of any size: char, nchar, varchar, nvarchar, text
• char -> int

https://docs.microsoft.com/en-us/previous-versions/dotnet/netframework-4.0/bb399548(v=vs.100)?redirectedfrom=MSDN

https://stackoverflow.com/questions/26303631/how-to-use-unsigned-int-long-types-with-entity-framework#:~:text=1%20Answer&text=Turns%20out%20that%20Entity%20Framework,What%20about%20ulong%20columns%3F

https://entityframework.net/knowledge-base/26303631/how-to-use-unsigned-int---long-types-with-entity-framework-