UpdatedAt is not set in the sample server with Azure SQL

[SorenBech2]

In the server/client sample the UpdateAt is not used. It is defined as nullable on the server side and not generated when a row is written to the table. The solution "works" since the null value is syncronized back and forth so as such not a bug. However I already have a database (Azure Mobile App) were the UpdatedAt field holds data and I'm struggling with converting this to CommunityToolkit.DataSync (Azure Sql on the server side and SQLite on the client side) as I haven't succeded in developing the correct conversion.

I have tried a host of options - to many to list here. It would therefore be great to have a working sample where the UpdatedAt is implemented - which I assume is necessary to manage the syncronization properly?

Appricitate your help in this.

[adrianhall]

There was indeed a bug in the server. I did not replicate the AzureSQL requirements for database triggers in the server. That is being done within prs/218

In the same PR, I've also added a test suite for testing the sample server, with the "UpdatedAt" create property test being the first in the set. I suspect that this set will continue to grow in the future.