This repository has been archived by the owner on Aug 2, 2024. It is now read-only.
Replies: 2 comments
-
On the client side, you don't want to set UpdatedAt at all - it's explicitly set by the server side. This is why the values in DataSyncTableData are not virtual. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Okay, that makes sense. In my scenario I'm wanting to maintain when the item was updated on the client, which for an offline client could be different than the time the item reached the server. I'll just add another property to keep track of that. Closing this discussion. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The
EntityTableData
class inMicrosoft.AspNetCore.Datasync.EFCore
has all its properties marked asvirtual
. This is nice since it give the option to override them if you want a different implementation of any of them than the default. However, the client class (Microsoft.Datasync.Client.DataSyncClient
) has non-virtual properties so there is no option to override these. Was there a particular reason for this?I want to override the
UpdatedAt
property on the client side so that it is set to the current time instead ofDateTimeOffset.MinValue
which it is by default.Beta Was this translation helpful? Give feedback.
All reactions