The database logic to save and retrieve data from database is handled by the Model layer of MVVM design pattern. All business logic of the app exists in this layer.
The View layer is just the UI of the application. The UI logic is handled in this layer like button click logic or page load logic or textbox blur logic etc. Sometimes, this layer is just the markup like html or xaml, and the events code is part of ViewModel layer rathern than the View layer.
The ViewModel provides data for the View like providing data for databinding controls and handles data updates from the View. Also, the ViewModel data is representing the current state of the View.
Note that any changes in ViewModel will automatically reflect in View and also any changes in the View will automatically reflect in the ViewModel part. In this sense, data flows/databinding is bi-directional in MVVM.
The database logic to save and retrieve data from database is handled by the Model layer of MVVM design pattern. All business logic of the app exists in this layer.
The View layer is just the UI of the application. The UI logic is handled in this layer like button click logic or page load logic or textbox blur logic etc. Sometimes, this layer is just the markup like html or xaml, and the events code is part of ViewModel layer rathern than the View layer.
The ViewModel provides data for the View like providing data for databinding controls and handles data updates from the View. Also, the ViewModel data is representing the current state of the View.
Note that any changes in ViewModel will automatically reflect in View and also any changes in the View will automatically reflect in the ViewModel part. In this sense, data flows/databinding is bi-directional in MVVM.