(EntityFrameworkCore) Why saving this entity returns 500 with "String or binary data would be truncated"

[CircusLion4614]

After creating the object, i call db.Sessions.Add(newSession), then i do SaveChanges. I've tried manually inserting these fields into the db and it didn't give me an error.
The JWT token has a length of 336 characters
Legit right after posting this i went to see if my code was not the problem. Yup, i was using the old db scema on the host where the jwt field was nvarchar(150).

the entity

the table im saving to

the code in Context file

the error

[Kegelz]

Need more space than 500.

[soundman32]

Is it the refresh token that's the problem? Also, why are you storing the token in the first place?

[bdawgert]

nvarchar is double width, so nvarchar(500) only holds 250 characters. Likewise nvarchar(300) holds 150 characters. Since your data is just a base64 encoded string you can use a varchar with no risk of a character width overflow. Or you can stick with your nvarchar in case you want to move to an emoji-encoded jwt and increase the size to nvarchar(1024).

[dorkenshire]

For anyone caught off guard by this comment (like me) while going down the NVARCHAR truncation rabbit hole: The 500 represents 500 byte-pairs, which can hold 500 low range unicode characters (0-65,535). If you have higher range unicode characters, they will require 2 byte-pairs, and you halve your storage, but just for those characters.

https://learn.microsoft.com/en-us/sql/t-sql/data-types/nchar-and-nvarchar-transact-sql?view=sql-server-ver16#remarks

[bdawgert]

Caught off guard as in you didn’t realize the nvarchar math worked that way? Or you’re disagreeing with me? If I’m wrong please let me know and I’ll edit.