Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0011451 | Openbravo ERP | A. Platform | public | 2009-11-20 20:32 | 2009-12-12 00:00 |
|
Reporter | networkb | |
Assigned To | shuehner | |
Priority | high | Severity | major | Reproducibility | always |
Status | closed | Resolution | no change required | |
Platform | | OS | 20 | OS Version | Community Appliance |
Product Version | 2.40MP10 | |
Target Version | 2.40MP12 | Fixed in Version | | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0011451: Time response of query generated by WAD is very high |
Description | In goodshipments window, in tab lines, the query generated by WAD to create a new record (set) is very slow when exists a lot of shipments. |
Steps To Reproduce | enviroment with 20.000 shipments and 200.000 shipments lines.
Sales Management || Transactions || Goods Shipment || Header >> Lines ->
edit line and click "save and new" button
the time to response is higher than 6 seconds |
Proposed Solution | |
Additional Information | |
Tags | No tags attached. |
Relationships | related to | backport | 0010989 | 2.40MP11 | closed | shuehner | Time response of query generated by WAD is very high | depends on | backport | 0011530 | 2.40MP12 | closed | shuehner | Time response of query generated by WAD is very high |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2009-11-20 20:32 | networkb | New Issue | |
2009-11-20 20:32 | networkb | Assigned To | => rafaroda |
2009-11-23 08:16 | rafaroda | Note Added: 0022084 | |
2009-11-23 08:16 | rafaroda | Assigned To | rafaroda => shuehner |
2009-11-23 10:29 | shuehner | Relationship added | related to 0010989 |
2009-11-23 11:21 | shuehner | Note Added: 0022100 | |
2009-11-23 11:43 | rafaroda | Note Added: 0022103 | |
2009-11-23 11:43 | rafaroda | Status | new => feedback |
2009-11-23 13:13 | rafaroda | Issue Monitored: rafaroda | |
2009-11-24 19:05 | networkb | Note Added: 0022144 | |
2009-11-25 10:08 | rafaroda | Note Added: 0022158 | |
2009-11-25 10:08 | rafaroda | Status | feedback => new |
2009-11-27 15:21 | rafaroda | Priority | immediate => high |
2009-11-27 15:21 | rafaroda | Status | new => scheduled |
2009-11-27 15:21 | rafaroda | fix_in_branch | => pi |
2009-12-11 16:22 | shuehner | Note Added: 0022712 | |
2009-12-11 16:22 | shuehner | Status | scheduled => closed |
2009-12-11 16:22 | shuehner | Resolution | open => no change required |
2009-12-12 00:00 | anonymous | sf_bug_id | 0 => 2912998 |
Notes |
|
|
Stefan,
Can you please comment on this Openbravo ERP 2.40 issue?
Thanks. |
|
|
|
According to the reporter i assume it is the same problem as in 10989 just in a different place. Some queries to not add the to_number function calls for id's. Which works in this case but can be quite slow, if the queried table contains many rows. Seems like the issue here is in some of the selectDef* methods generated by wad.
If this is the same issue as in 10989 then it concerns only 2.40 and only postgres. |
|
|
|
Thank you very much for your comments Stefan.
@networkb: 0010989 seems to have been fixed in Openbravo ERP 2.40 MP11. Please try to reproduce this issue there and inform about the result.
Thanks. |
|
|
|
i have applied the patch of 10989 ticket and the time is better in some queries, but to create new record in this window, the time is very high. |
|
|
|
Stefan, should we schedule this defect? |
|
|
|
Issue is only related to 2.40 and postgres >=8.3. Closing defect, 2.40 will be handled in the scheduled backport. |
|