That too. Though I used efficiently in a sense of minimizing the communication between client/server by normalizing data and just sending changes. Which is eas

That too. Though I used efficiently in a sense of minimizing the communication between client/server by normalizing data and just sending changes. Which is easier if you keep data normalized on the client side too, and look up related objects in a Map when needed, instead of keeping multiple copies of objects representing the same entity everywhere in your client code in some/vasrious denormalized forms. It would actually be very nice for some use cases if I had a SQL interface to local data on the client side too, so that I can query/join them up arbitrarily as needed from what's loaded up to client storage. That's unpleasant to do in the browser with current platform APIs. Basically I want WebSQL back in some form, instead of this IndexedDB thing. :)