Is there a way to reload/refresh?

[fbertuzzi]

Hey,

I'm currently trying to reload a @Query as my database is changed on another Process (NotificationService Extension to be exact).
I'm using a DarwinNotificationCenter as described here to notify my view.

The problem that I have now, is that I can't reload the @Query at least I don't know how to do it.
As it's not a State variable I cannot modify it. Is there maybe a builtin way in @Query or GRDB itself, which I don't know of to trigger a refresh?

[groue]

Hello @fbertuzzi,

The solution lies in the publisher you return from your Queryable type. For example, turn the Darwin notifications into a publisher that you use to restart the ValueObservation publisher.

And this now turns into a question about Combine more than about GRDBQuery ;-)

You should end up with something akin to:

darwinNotificationPublisher
    .map { _ in /* some ValueObservation publisher */ }
    .switchToLatest()

[fbertuzzi]

Hey @groue,

Thank you for the super fast reply!
Would "restarting" the ValueObservation use the updated data in the Database File or is there more I need to do like closing and reopening the AppDatabase?

[groue]

Thank you for the super fast reply!

I just happened to open the lid of the computer, and there you were ;-)

Would "restarting" the ValueObservation use the updated data in the Database File or is there more I need to do like closing and reopening the AppDatabase?

You have nothing more to do: the ValueObservation will do its usual job, which is to publish the current (i.e. on disk) database value on subscription, and then wait for modifications performed in the main process. There is no cached stuff or things like that. It's really "just" a Combine puzzle.

[fbertuzzi]

I just happened to open the lid of the computer, and there you were ;-)

I guess I'm pretty fortunate then!

You have nothing more to do: the ValueObservation will do its usual job, which is to publish the current (i.e. on disk) database value on subscription, and then wait for modifications performed in the main process. There is no cached stuff or things like that. It's really "just" a Combine puzzle.

Okay thats good! Shouldn't be that difficult then.
Thank you for your help!

[groue]

You're welcome :-) Happy GRDB!