Understanding problem

[w4mike]

Hi dear vuex-orm-next team,

to decide using this project or not I need to clarify one question:

I am currently writing my own ERP+CRM+Email+... system.
For the frontend I will be using the quasar framework.
The plan is to use vuex-orm-next + the axios plugin.
The user can travel around different components like email, fax, offer, order, ...
This will be different pages with tabbed components/pages, where the first tab is always the list of all items with dynamic scroll (content loaded from server as needed), and each detail item will be a new tab with a detail form.
Of course I want to keep the current states when user is travelling to other modules, so I will be using massively vue's keep-alive directive.

Now the question is, what will happen with vuex-orm-next ?
In worst case will it end up that the whole database is loaded into memory of the browser, or do I need to handle switch between different views and need to reload the data from the server ?

Sorry, for potentially stupid question, but just started with vue, vuex, ...

Many thanks for your answer,
Mike

[cuebit]

In worst case will it end up that the whole database is loaded into memory of the browser, or do I need to handle switch between different views and need to reload the data from the server ?

Vuex is a global state management library. Anything you add to global state will be in memory until it is withdrawn. Since Vuex ORM supplements Vuex, any data you add to it will of course be added to the global state. Of course, as with Vuex, you're free to add/remove data from global state as you please and whatever works for your application. Bear in mind, you'd need a substantial amount of data for memory to be a cause for concern. I wouldn't overthink it.

The plan is to use vuex-orm-next + the axios plugin.

If you're referring to the plugin-axios-next for Vuex ORM, I would recommend reading this issue.

[kiaking]

Closing due to inactivity. Please open another issue if there's anything!