Change umbracoKeyValue SQL type to nvarchar(max)

[Rockerby]

Currently, the database table umbracoKeyValue has a value type of nvarchar(255) which limits the amount of data you can put in there. Could this be increased to nvarchar(max) to store more data?

Use cases for this could be for custom development where you want to store oAuth response objects, dynamic configuration (change during runtime) or for storing JSON data, to name a few. The current alternatives if you want to store more than 255 chars include creating your own custom data storage (like file-based or custom database tables).

This also causes potential issues if you develop using SQL Lite as that doesn't have the 255 constraint but will then break when migrating to a production SQL server.

[lassefredslund]

Hi @Rockerby.
I think it would be totally OK if this field was nvarchar(max).
I'll add it as "up for grabs".

[Rockerby]

Thanks @lassefredslund

Just to keep this up to date, change made and PR 14085 created