git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30396 20353a03-c40f-0410-a6d1-a30d3c3de9de

First version of delivery_solver refactored interface. Names were chosen not to conflict with existing solvers.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30395 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30394 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30393 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30392 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30391 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30390 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30389 20353a03-c40f-0410-a6d1-a30d3c3de9de

Added comment to explain that explain should not return a list but a single message (divergence testers should not test multiple divergences at the same time if divergences can be resolved using different solvers).

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30388 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30387 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30386 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30385 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30384 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30383 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30382 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30381 20353a03-c40f-0410-a6d1-a30d3c3de9de

First version of target_solver refactored interface. Names do not conflict with existing solvers because target solvers are now ERP5 Documents.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30380 20353a03-c40f-0410-a6d1-a30d3c3de9de

First version of delivery_solver refactored interface. Names were chosen not to conflict with existing solvers and to show that delivery solvers are about quantity.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30379 20353a03-c40f-0410-a6d1-a30d3c3de9de

For example one simulation movement quantity -1 and another simulation movement
of quantity 1 that becomes one delivery movement of quantity 0.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30378 20353a03-c40f-0410-a6d1-a30d3c3de9de

division and setting a quantity ratio of 0)


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30377 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30376 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30375 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30374 20353a03-c40f-0410-a6d1-a30d3c3de9de

add a test to check if PropertyTypeValidity (that is enabled everywhere) works fine if property is not accessible by user (eg. source_title property in Arrow property sheet is not accessible if source value is not accessible). Currently this test raises Unauthorized error, and will be fixed later.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30373 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30372 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30371 20353a03-c40f-0410-a6d1-a30d3c3de9de

replace transaction subcommits (deprecated since Zope 2.8 or before) with optimistic savepoints, which do the same thing.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30370 20353a03-c40f-0410-a6d1-a30d3c3de9de

Boolean type exists since Python 2.3. We don't need at all the compatibility with Python 2.2 or older.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30369 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30368 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30367 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30366 20353a03-c40f-0410-a6d1-a30d3c3de9de

- if an alarm is not enabled, it should not be effective
- if an alarm is expired, it should not be effective
- an alarm should not be invoked only because it gets enabled




git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30362 20353a03-c40f-0410-a6d1-a30d3c3de9de

* Accept NULL for alarm_date.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30361 20353a03-c40f-0410-a6d1-a30d3c3de9de

* Stop setting a bogus default to alarm_date.
* Index alarm_date as well.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30360 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30359 20353a03-c40f-0410-a6d1-a30d3c3de9de

If not enabled, alarm date should be None. Also, fix the test of tic. I think it was working only by chance.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30358 20353a03-c40f-0410-a6d1-a30d3c3de9de

* Clean-up the form, ReturnedSalePackingListModule_viewReturnedSalePackingListList, according to sale/purchase packing list module.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30357 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30356 20353a03-c40f-0410-a6d1-a30d3c3de9de

_filterCategoryListByPermission must consider that _getSingleCategoryAcquiredMembershipList may not always include a base category in the result.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30355 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30354 20353a03-c40f-0410-a6d1-a30d3c3de9de