0026157: Web POS doesn't reset the database if the modules or the Web POS itself change

Description

Currently there are methods in the Web POS which check if the database version is too old, and reset the whole database in case the version changed. This is done to ensure that the structure of the database corresponds to what is defined in the current version of the Web POS sources.

However, this mechanism doesn't work correctly. The main problem is that the version of the local database is compared against a hardcoded value contained in the login-model.js file. This hardcoded value is not being updated automatically, and moreover, it's not taking into account the fact that external modules could be installed in the system, and they could be updating the database structure too.

Steps To Reproduce

- Update the Web POS.
- Go to the Web POS URL. Realize that the database was not reset even if the Web POS was updated.

Proposed Solution

The database version should be dynamically generated from the versions of the Web POS module plus all the modules which depend on it, in a similar way as the UUID which is generated for the Javascript file which contains all static resources (it could even be the same UUID).

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

duplicate of

defect

0029055

RR15Q2

closed

marvintm

Web POS doesn't handle update of local database tables correctly

Notes
There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
2014-04-03 11:07	marvintm	New Issue
2014-04-03 11:07	marvintm	Assigned To	=> marvintm
2014-04-03 11:07	marvintm	Triggers an Emergency Pack	=> No
2016-03-09 09:40	marvintm	Review Assigned To	=> marvintm
2016-03-09 09:40	marvintm	Relationship added	duplicate of 0029055
2016-03-09 09:40	marvintm	Status	new => closed
2016-03-09 09:40	marvintm	Resolution	open => duplicate
2016-03-09 09:40	marvintm	Fixed in Version	=> RR15Q2