Closed seadowg closed 5 days ago
Datasets are downloaded and stored for every form
Should this consideration be part of #6029?
Currently I think the only case that a download would happen for multiple forms is if an entity list changed part way through a match exactly sync. Otherwise, there would be a server request, but the server would immediately respond with a 304 and the entity list would be returned from cache. But yes, each entity list is stored once for each form.
Should this consideration be part of https://github.com/getodk/collect/issues/6029?
I think it probably gets ticked off as part of that, but it's a different problem so I'd like to keep it called out separately.
I'm closing this as it's now easier to just track entity work as a normal part of the backlog than here.
I was just about to update with some notes on release timeline and current limitations (eg no integrityUrl)! I think it would be helpful to have that info tracked alongside open issues. Maybe it’s a new meta issue?
I was just about to update with some notes on release timeline and current limitations (eg no integrityUrl)! I think it would be helpful to have that info tracked alongside open issues. Maybe it’s a new meta issue?
Maybe a doc? I do agree it would be good to have some shared thoughts on all that.
Release blockers (prioritised):
To improve:
row_number()
for DB queries on API 29+