Project:
View Revisions: Issue #33519 | [ Back to Issue ] | ||
Summary | 0033519: Masterdata loading fails when pagination is used | ||
Revision | 2016-07-26 11:58 by marvintm | ||
Steps To Reproduce | There are two ways to reproduce the problem: - Find a database with many records (more than 35000 in one model, for example products or business partners). Log in the Web POS, and verify that not all records are in the local database. An easier way (and advisable for the developer who will be fixing the problem) is the following: - Log in the Web POS, go to Chrome Developer Tools, and execute the query in the local database: select count(*) from m_product Verify that there are 164 records in the table. - Then, go to file ob-datasource.js. - Find this line: handleIncrementalRequest(35000, 0, params, incremental); and change it to: handleIncrementalRequest(20, 0, params, incremental); - Clear cache and log in the Web POS again. - Execute the same query in the local database. Verify that there are 162 products. There were two products lost at some point, and this is wrong. |
||
Revision | 2016-07-26 11:27 by marvintm | ||
Steps To Reproduce | There are two ways to reproduce the problem: - Find a database with many records (more than 35000 in one model). Log in the Web POS, and verify that not all records are in the local database. An easier way (and advisable for the developer who will be fixing the problem) is the following: - Log in the Web POS, go to Chrome Developer Tools, and execute the query in the local database: select count(*) from m_product Verify that there are 164 records in the table. - Then, go to file ob-datasource.js. - Find this line: handleIncrementalRequest(35000, 0, params, incremental); and change it to: handleIncrementalRequest(20, 0, params, incremental); - Clear cache and log in the Web POS again. - Execute the same query in the local database. Verify that there are 162 products. There were two products lost at some point, and this is wrong. |
Copyright © 2000 - 2009 MantisBT Group |