- 09 Oct, 2015 1 commit
-
-
Jérome Perrin authored
When searching accounts by validation state, the stat of number of movements on an account could be wrong
-
- 08 Oct, 2015 3 commits
-
-
Vincent Pelletier authored
-
Jérome Perrin authored
-
Julien Muchembled authored
ERP5Site.log and Base.log are wrappers to the 'log' function from Product.ERP5Type.Log, but parameters were forwarded in a wrong way when called with a single argument: self.log(message) # Base method This was equivalent to: log(message, '') # function from Product.ERP5Type.Log And the whole message was later part of subsystem in: logger = logging.getLogger(subsystem) But because loggers are never freed, it is important that 'subsystem' does not vary too often, to avoid a memory leak. The fix is to simply forwarding parameters with catchall arguments, instead of duplicating the signature from Product.ERP5Type.Log. Of course, it remains important to call these methods correctly, otherwise memory leaks can happen again. For this reason, catchall arguments also prevents ERP5Site.log and Base.log to be called by ZPublisher. Reported-by: Kirill Smelkov <kirr@nexedi.com> Reviewed-by: Kirill Smelkov <kirr@nexedi.com>
-
- 07 Oct, 2015 8 commits
-
-
Kazuhiko Shiozaki authored
Now you can sort results by full text search score, for example.
-
Kazuhiko Shiozaki authored
Now we have explicit ORDER BY in the outer query so that we no longer need to disable derived_merge optimizer. c.f. https://bugs.launchpad.net/maria/+bug/985828
-
Kazuhiko Shiozaki authored
- group_by, group_by_expression -> group_by_list - select_list, select_expression -> select_dict - sort_on, sort_on_order, order_by_expression -> order_list
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
It is useful when use select_expression in inner query and use group_by_expression or order_by_expression in outer query.
-
Kazuhiko Shiozaki authored
Revert "Add auto_extend_select_list argument in buildSQLQuery() and use alias in group_by_expression and order_by_expression." Revert "Support group_by_list and order_by_list in WebSection_getDocumentValueList." Revert "Support order_by_list in Resource_zGetMovementHistoryList." No need to extend SQLCatalog parameter to support group_by_list and order_by_list in sub-queries.
-
Kazuhiko Shiozaki authored
It should be only for the case where no predicate criterion exists at all.
-
- 06 Oct, 2015 16 commits
-
-
Kazuhiko Shiozaki authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
forge: do not link to Bug portal_type base categories that are already provided by Bug property_sheet
-
Vincent Pelletier authored
-
Jérome Perrin authored
-
Jérome Perrin authored
Added in keep path list, for compatibility
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
configurator: add an empty item in "Select your accounting plan" to make sure the user really selects
-
Jérome Perrin authored
-
Vincent Pelletier authored
Catalog discards empty string, so this code path's only effect is causing log activity.
-
Kazuhiko Shiozaki authored
Also move 'call_traceback' to 'More Columns'.
-
- 05 Oct, 2015 1 commit
-
-
Romain Courteaud authored
-
- 04 Oct, 2015 3 commits
-
-
Kazuhiko Shiozaki authored
Now we have explicit ORDER BY in the outer query so that we no longer need to disable derived_merge optimizer. c.f. https://bugs.launchpad.net/maria/+bug/985828
-
Kazuhiko Shiozaki authored
Now you can sort results by full text search score, for example.
-
Kazuhiko Shiozaki authored
Add auto_extend_select_list argument in buildSQLQuery() and use alias in group_by_expression and order_by_expression. If True, select_list is automatically extended to have columns used in group_by_list and order_by_list. It is useful when use select_expression in inner query and use group_by_expression or order_by_expression in outer query.
-
- 02 Oct, 2015 3 commits
-
-
Cédric Le Ninivin authored
-
Sebastien Robin authored
Remove broken concept of Mapping Properties that was used on legacy simulation. We do not want to use this concept any more, any mapping should be done by rule themself. Removing mapping properties leads to more generic concepts and much simpler code. With legacy simulation, in case of returned sale packing list (in case we want to invoice in same sale invoice usual sale packing list and returned sale packing list) : AR (delivering_rule): -> SM (source/A, destination/B) -> AR (invoicing_rule, having mapped_property mapping source to destination and vice versa) -> SM (source/A, destination/B) builders and solvers where doing sm.getMappedProperty('source') which was equivalent to sm.getProperty('destination'), thus the mapping was done in live time Now in such case, we should implement mapping directly at rule level, and this should give: AR (delivering_rule): -> SM (source/A, destination/B) -> AR (invoicing_rule, reversing source and destination) -> SM (source/B, destination/A) here we directly have properties we wish, no need of hacks on builders and solvers
-
Sebastien Robin authored
Remove broken concept of Mapping Properties that was used on legacy simulation. We do not want to use this concept any more, any mapping should be done by rule themself. Removing mapping properties leads to more generic concepts and much simpler code. With legacy simulation, in case of returned sale packing list (in case we want to invoice in same sale invoice usual sale packing list and returned sale packing list) : AR (delivering_rule): -> SM (source/A, destination/B) -> AR (invoicing_rule, having mapped_property mapping source to destination and vice versa) -> SM (source/A, destination/B) builders and solvers where doing sm.getMappedProperty('source') which was equivalent to sm.getProperty('destination'), thus the mapping was done in live time Now in such case, we should implement mapping directly at rule level, and this should give: AR (delivering_rule): -> SM (source/A, destination/B) -> AR (invoicing_rule, reversing source and destination) -> SM (source/B, destination/A) here we directly have properties we wish, no need of hacks on builders and solvers
-
- 01 Oct, 2015 1 commit
-
-
Cédric Le Ninivin authored
-
- 30 Sep, 2015 1 commit
-
-
Vincent Pelletier authored
Documents should inherit from XMLObject, which already overloads this setter. As a result, this method is normally not used. The problem is that it gets called when calling newTempBase( description='foo' ) which fails with: AttributeError: _setDescription because _setProperty finds setDescription and tries to call it, instead of setting description as a local property..
-
- 29 Sep, 2015 3 commits
-
-
Kazuhiko Shiozaki authored
-
Kristopher Ruzic authored
-
Kristopher Ruzic authored
doesn't allow for offline use however
-