https://bugs.kde.org/show_bug.cgi?id=442918
--- Comment #2 from ro...@bumblepuppy.org --- Wow, thanks so much for such a comprehensive reply Simon, that's very helpful. It seems the more I get involved with dev on Android, the more I realise it's an endless series of exceptions, everyone has their own special way of doing a thing, with little advantage gained to the wider ecosystem/other developers/users. The database access method does indeed sound screwy, not at all efficient or good practice. > it would take the same amount of time to update that cache as it does today > to load messages, I assume there is no metadata stored anywhere to say "this message/conversation has changed since it was last synced"?. I'm thinking of the model which "unison" uses to store sync information. Your suggestion of "try the best method, fail to the lowest-common denominator if necessary" sounds like a good step forward, I'd love to volunteer my time, but it's a bit beyond my skills I'm afraid. -- You are receiving this mail because: You are watching all bug changes.
