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

only be enabled in unit tests.
It uses pickle to check if the object is persistent or not, I'm too lazy to do
this by iterating in gc.get_referents graphs.


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

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

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

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

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

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

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

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

archive, because inventory computation depends on the catalog


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

explicitly specified, thus we index everything at one time preventing
from retrieving same objects many times from different node


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

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

method_id on objects with the same portal type (for instance, asPredicate,
during a predicate search), caching its result is much faster than looking for
the same script in a nearly identical acquisition path each time.


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

Use timestamp instead of DateTime.


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

Do not use -1 value in "processing" column (it duplicates the information already provided by "processing_node=-1").
This allows to check this column for equality instead of inequality, thus making a better use of indexes.


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

reindex by a script specifying request parameter and properties used


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

Use representations of values instead of bare values to make error message easier to eyeball.


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

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

when cataloging in stock, check not isInventoryMovement at filter level thus avoiding deleting temporary line of inventory

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

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

catalog or not


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

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

get height for usual Planning Box (before was only calculated for stastistic)



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

Remove tri_encaisse_externe case, it's not supposed to be handled in this part of the application...


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

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

* Enlarge link area to whole tab

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

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

Fix an error in query generation when there is just one criterion in worklist (including security criterion if any).


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

- created new 751

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

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

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

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

in the sequence.
This insert something like this in the traceback:
   stepA
   stepB
>  stepA
   stepB





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

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

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

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

generateNewId would not work the first time it is called


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

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

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

Please do not use this field, which it unstable and unsafe.


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