Push in the background while still allowing changes to be saved

[scout208]

I have some clients that are running on very slow internet connection, and it can take them a long time to push data. I would like to be able to have the PushAsync method run in the background so that users don't have to wait a long time for it to finish and can continue adding new data to the service. The problem I have found is that if I have PushAsync running on a different thread, then any calls to SaveChanges will hang. Is there any way to work around this?

[adrianhall]

You are running into lock contention.

Basically, both PushAsync and SaveChanges read/write from a shared table - SQLite is single threaded, so we put a lock around that critical section. This is limited to the table being pushed normally. Without those locks, your tables would quickly get into merge conflict area.

There are definite strategies for doing what you want, but they involve a temporary table and merging in your changes after the push.