Omitting columns from the sync process

Discussed in https://github.com/Azure/azure-mobile-apps/discussions/680

<div type='discussions-op-text'>

^{Originally posted by henda79 May 25, 2023} I have some tables which have columns and are really only for the client. Is there a way to omit these from the sync ? I thought about some of the annotations I could use on the properties but ones like JsonIgnore would stop the column been created on the client wouldn’t it ?!?

What’s the best way to go about this if any ?

Also, is it possible to have table(s) in the database which does not sync at all. It seems overkill to have another database and all the fluff that comes with it for the sake of 1 or 2 tables.

Thanks !</div>

[adrianhall]

Potentially. It’s one of those “what happens at reflection vs. what happens with serialization” questions. It’s not clear. The short version is that the assumption is that the local db == remote db in form, and if necessary, the remote db is a superset of the local db. We are now proposing to break that assumption, so lots of things likely break.

[amertlich]

SQLite handles concurrent reads very well. It’s the concurrent writes that are the potential problem. But since we control things from the same process and know how our database is accessed (through a shared DI service) we can synchronize writes in scenarios where we anticipate that happening.