Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0026589Retail ModulesWeb POSpublic2014-05-19 11:192015-05-12 11:17
ReporterOrekaria 
Assigned ToOrekaria 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionduplicate 
PlatformOS5OS Version
Product Version 
Target VersionFixed in VersionRR15Q2 
Merge Request Status
Review Assigned Tomarvintm
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0026589: Stabilization: When the backend generates a new uuid.js, chrome does not update/delete the Web SQL database
DescriptionWhen the backend generates a new uuid.js, chrome does not update/delete the Web SQL database
Steps To ReproduceOpen the WebPOS

1. In the console, look for the client javascript file e,g: http://localhost:8080/openbravo/web/js/gen/45436561cf4d0380b1d61fba0439fa53WebPOS.js [^]
2. Perform a change to any .js in a module that has already been set as 'in development'
3. refresh the client
4. check that the javascript file has changed

Proposed SolutionMaybe...

in the backend, warn the client to only update when all the clients have commited their operations (sells, cashups, etc). This is how it should be right now, no change here.

- detect when the generated javascript has changed
- then detect if there are pending commits (orderloader, cashup, etc), warn the user that this will be lost and that he/she will have to obbey the backend warning
- then delete the chrome Web SQL database
- then create the new Web SQL database
Additional Information
TagsNo tags attached.
Relationships
related to design defect 0027216 new marvintm Stabilization: Web POS should not login if the database is not consistent or a table is empty 
related to design defect 0027228 new marvintm Stabilization: Web POS should validate that models have been imported properly to Web POS 
related to defect 0027413 new Retail Stabilization: It should never ever be necessary to clear cache. 
blocks feature request 0027329 new Retail Stabilization: Overhaul the loading process (since the url is entered until the webpos has loaded) 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-05-19 11:19OrekariaNew Issue
2014-05-19 11:19OrekariaAssigned To => Orekaria
2014-05-19 11:19OrekariaTriggers an Emergency Pack => No
2014-08-17 18:08OrekariaRelationship addedblocks 0027329
2014-08-18 15:04OrekariaProposed Solution updated
2014-08-18 15:05OrekariaRelationship addedrelated to 0027216
2014-08-18 15:05OrekariaRelationship addedrelated to 0027228
2014-08-18 15:10OrekariaRelationship replaceddepends on 0027329
2014-08-22 09:29OrekariaRelationship addedrelated to 0027414
2014-08-22 09:30OrekariaRelationship addedrelated to 0027413
2014-08-22 09:31OrekariaSummaryWhen the backend generates a new uuid.js, chrome does not update/delete the Web SQL database => Stabilization: When the backend generates a new uuid.js, chrome does not update/delete the Web SQL database
2014-08-22 09:51OrekariaRelationship replacedblocks 0027329
2014-08-24 06:58OrekariaNote Added: 0069665
2015-05-12 11:17marvintmReview Assigned To => marvintm
2015-05-12 11:17marvintmNote Added: 0077332
2015-05-12 11:17marvintmStatusnew => closed
2015-05-12 11:17marvintmResolutionopen => duplicate
2015-05-12 11:17marvintmFixed in Version => RR15Q2

Notes
(0069665)
Orekaria   
2014-08-24 06:58   
If the manifest is sent with a 404 code, the manifest is invalidated
(0077332)
marvintm   
2015-05-12 11:17   
This has been fixed as part of the local database update refactor.