@IonicGeoff wrote:
I have quite a bit of experience using relational databases and I’m wondering what is the best way of storing a “lot” of related data using LocalStorage.
For example, if I was writing an invoice app with customer and invoice data, I could store all the data in one storage object i.e. store all the customers and all the invoices in one storage object
Or, I could split it to have a separate storage object for EACH customer, or one storage object for ALL customers, and similarly a separate local storage object for ALL invoices, or each invoice?
Logically I would think that performance would be better if the data was split, and I only loaded whatever data was needed? Is this the case?
If there wasn’t going to be much data I would stick it all into one object, for convenience.
Posts: 1
Participants: 1