Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • I think 2 is the best - reacting to those which are recorded as actually deleted - falling back to 3 if necessary. Commented Jul 29, 2024 at 14:33
  • 1
    if the user has clicked on a row to delete it, and the delete method hasnt errored, you can just remove the row they clicked on Commented Jul 29, 2024 at 15:31
  • I used to just have an event “database changed”. Plus a method that wouldn’t read an object from the database, but pass an existing object, update it with the contents of the database, returning a Boolean whether there was any change. That was plenty fast on an iPhone 5. With a GUI where every object could have a different height. Commented Jul 29, 2024 at 16:42
  • 1
    You get around many performance problems if your GUI library has a well - performing class for tables. For example, an iOS table view stores one table view cell per table row that is displayed. Your table may have 200,000 items but only 20 cells on the screen are actually used at any time. The same cells are reused for whatever item they display at the moment. Commented Aug 1, 2024 at 16:55