BulkSaveChangesAsync trims spaces in SQL server:
Lets say I have value "X" and update it to "X " - this is totally ignored and in the DB there is no update to "X ".
If I update "X" to "XX " - it works as expected and I can see spaces.
The optimization seems to works like this: if we have 5 symbols in DB and add 6th symbol as space - it is ignored totally to save some bytes and in the end we do not do the update of that field at all in the MERGE statement.
BulkSaveChangesAsync trims spaces in SQL server:
Lets say I have value "X" and update it to "X " - this is totally ignored and in the DB there is no update to "X ".
If I update "X" to "XX " - it works as expected and I can see spaces.
The optimization seems to works like this: if we have 5 symbols in DB and add 6th symbol as space - it is ignored totally to save some bytes and in the end we do not do the update of that field at all in the MERGE statement.