Force sqlite-data queries to fetch updated changes

[okmaybenot]

I’m using an App Group container to share an SQLite database between the main app and a share extension, but sometimes changes made in the extension aren’t visible in the app. What is the proper way to force queries to fetch the latest changes?

[mbrandonw]

Hi @okmaybenot, you should know that putting SQLite databases in app group containers is precarious. There was a discussion recently about this here #294, and there's an article you should read here.

[okmaybenot]

Thank you, that's unfortunate.

[okmaybenot]

Also, @mbrandonw, putting App Groups issue aside and returning to the OP, I think I still have a few cases where I’d like to trigger Queries after something unrelated changes. What’s the best way to do that? Probably I could update some unrelated piece of state, but I’m not sure that’s the right approach.

Thank you!

[mbrandonw]

Can you explain more what you mean by "something unrelated changes"?

In general the @FetchAll/@FetchOne/@Fetch property wrappers observe changes to the database and will automatically update views when they see changes.

[okmaybenot]

Sure! Here’s the situation:

• I show a list of items using Fetch.
• I load images (which are not direct part of the item) lazily when a cell appears on screen.
• I can open an item’s detail view and change its image, then go back to the list.
• When I return, the old image is still displayed in the list until I switch tabs or something.

I could probably include the image ID in the selection of items, but I wanted to get a simpler solution working first.

[okmaybenot]

Hmm debugging a bit more, I think the issue isn’t that the Query isn’t being refetched, but that the .task on the cell where I fetch the image isn’t being called. For now, I’ve worked around it by using .task(id: UUID())

Anyway, thanks a lot!