|View Issue Details|
|Type||Category||Severity||Reproducibility||Date Submitted||Last Update|
|defect||[Retail Modules] Web POS||major||always||2012-09-06 17:40||2012-09-25 13:09|
|Priority||urgent||Resolution||fixed||Fixed in Version|
|Status||closed||Fix in branch||Fixed in SCM revision||2048cbce78b5|
|OS Version||Database version||Ant version|
|Product Version||SCM revision|
|Review Assigned To|
|Regression introduced in release|
|Regression introduced by commit|
|Triggers an Emergency Pack||No|
0021573: Change in local tables in different versions of the Web POS needs to be managed
|Description||Currently, the local tables are automatically created when a user logs in the Web POS initially, and then, are not touched again.|
This will be a problem when subsequent versions of the Web POS (which will include changes in the structure of these tables) are released.
The structure of these tables needs to be updated (probably by droping and creating the tables again), when a change in the database version is detected.
Moreover, the unlikely but theoretically possible case of offline terminals which reconnect to an updated OB server needs to be managed, to prevent data loss in case of pending-to-be-sent tickets.
|Steps To Reproduce||The problem will happen when users update to the next version of the POS.|
|Tags||No tags attached.|
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Thu Sep 20 13:11:27 2012 +0200
URL: http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/2048cbce78b51480bb0f3a91701f3d87f3040c6b [^]
Fixed issue 21573. The following changes have been made:
- Now the database version change will be detected. If the version changed, the model tables will be dropped.
- To avoid losing data on the client side, a particular check will be done if a change is detected in the application cache: if there are no pending tickets, the page will be reloaded (at this point, a change in the database version will be detected, and the tables will be dropped). If there are pending tickets, a popup will be shown, and the user will be compelled to log in and complete his tickets. Once the page is reloaded, the database version change will be detected, and the tables will be dropped.
This issue has now been fixed, which means that the system will automatically recreate the database when the version of the database itself has changed.
It is very important that System administrators understand that it is their responsibility to ensure that all POS terminals have no pending tickets before updating the POS module. After the POS module has been updated, the client will display a warning to the user in case there are still pending tickets, and the user has only one shot to complete them. After that, the next time the page is reloaded, the application cache triggers in, and the database will be recreated, so all pending data will be lost.
|2012-09-06 17:40||marvintm||New Issue|
|2012-09-06 17:40||marvintm||Assigned To||=> adrianromero|
|2012-09-06 17:41||marvintm||Priority||normal => urgent|
|2012-09-20 13:08||marvintm||Assigned To||adrianromero => marvintm|
|2012-09-20 13:12||hgbot||Note Added: 0052259|
|2012-09-20 13:12||hgbot||Status||new => resolved|
|2012-09-20 13:12||hgbot||Resolution||open => fixed|
|2012-09-20 13:12||hgbot||Fixed in SCM revision||=> http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/2048cbce78b51480bb0f3a91701f3d87f3040c6b [^]|
|2012-09-21 11:04||marvintm||Note Added: 0052272|
|2012-09-25 13:09||adrianromero||Status||resolved => closed|
|Copyright © 2000 - 2009 MantisBT Group|