You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the app pulls all the records from the database on document.ready() (with a GET), and then searches among those. This is fine with our tiny sample set, but it will be very slow once we're working with real data. I'm not sure what the right way to do this is. We probably want to use some server-side sorting and filtering, instead of doing it all in the client.
The text was updated successfully, but these errors were encountered:
This will require the addition of a search endpoint to the API -- I'd like to avoid adding that type of endpoint for this round simply because we should first get alignment on the existing endpoints across the openhmis discussion list.
Currently, the app pulls all the records from the database on document.ready() (with a GET), and then searches among those. This is fine with our tiny sample set, but it will be very slow once we're working with real data. I'm not sure what the right way to do this is. We probably want to use some server-side sorting and filtering, instead of doing it all in the client.
The text was updated successfully, but these errors were encountered: