uid is used internally during recursive calls and using uid can lead to
traverse all lines of catalog.

Note: Generic code shall have no constraints at all.

Conflicts:

	bt5/erp5_accounting/bt/revision

It will protect against storing truncated data.

If 2 lines have the same effective date (catalog has a 1 second precision),
always return the validate and open first.

Commit: 02d06501

Changes applied from history:

http://git.erp5.org/gitweb/erp5.git/history/refs/heads/interaction-drop:/product/ERP5/Document/SubscriptionItem.py?js=1

Original commit from : Lukasz Nowak <luke@nexedi.com>
                       3e45ec35

From Lukasz Nowak:

1- Compensation is undesired. (51c8a250)

  Raise loudly with message.

2- Disallow any compensation. (3c74ed07)

3- Emit more informative log. (534b2e77)

Also minimise activity hurricane by calling expand directly.

Open Orders are searched using indexation timestamp, which allows to see them
in "windows", and does not repeat expand if not needed.

Generate activities and allow to pass the tag. Use search and activate
everywhere which will allow to walk through objects without killing the cluster
even in case of really big documents.

Avoid calling isDivergent which can take few minutes to finish.

causality_state comes from well designed causality workflow, which informs
enough about delivery state. Fetching causality_state property is extremely
fast.

Notes:

Do nothing on 'calculate' instead of disabling *_causality_interaction_workflow as
these interaction workflows do not generate activities directly, and do work
that can't be postponed.

By contrast, 'calculate' transition of delivery_causality_workflow is modified
so that no 'updateCausalityState' activity is created by default.

This commit also update list of method_id which should not call calculate_causality

Conflicts:
	bt5/erp5_crm/bt/revision

 - Acquire subordination from parent Computer: Thanks to this Computer Partitions
     can be in same category as Computers they are contained in.

 - Computer should acquire region from parent.
 - Add group acquisition on Computer Partition

According to Payzen API, boolean should be translated into 0 or 1 in order to be part of the signature.
The only value which contains a boolean is "litige" which can cause signature miss-match without
this change.

  Reimplement for follow up the migration of PropertySheets from Products to ERP5

  Normally it should work as annonymous.

the selection name is duplicated with Computer_view/listbox

It can be used with an external method by providing the URL to proxy as a query parameter:
ERP5Site_getHTTPResource?url=URL

The query is synchronous (no portal_activities), so, the Zope thread will be blocked until the external request is other.
In order to prevent consuming all threads, there is a really aggressive timeout of 1 second only.
This is enough for a RSS reader.
If the timeout is to short, do not increase it, but change the proxy design to use portal_activities instead.

For now, only authenticated user can use it (to prevent becoming an open proxy).
Only GET query are allowed (until a use case required any other HTTP method).

Instead of using obsolete processing_node parameter, use invalid_onlym
with True, in order to check if there are activities with error.

As INVOKE_ERROR_STATE is needed only in SQLBase, move it there and so drop it
from ActiveObject and ActiveProcess.

Thanks to using invalid_only the caller can check if there is any
invalid activity on the context.

This might be used by hasErrorActivity in ActiveObject and
ActiveProcess.

hasErrorActivity is tested on ActiveObject and ActiveProcess classes.

DISTRIBUTABLE_STATE was removed bad50097

Writing SQL belongs to catalog.

Improvement: As proposed by Jean-Paul when this extension was added (2010),
allows mixing left- and inner-join lookups.
Improvement: Now it is not required to specify tested_base_category_list
to enable inner joins: they will automatically be used whenever a base
category set on context matches the preference. If all categories set on
context match the preference, then no left join will be used at all.

This only makes a difference when "test=False" is given, which is a hack
anyway.

The main purpose is to stop calling buildSQLSelector so it can be removed.
Remove Base_zSearchRelatedObjectsByCategoryList.
Also, discard a superfluous comment in testArchive which references the
discarded ZSQLMethod, for consistency.
Fixes an existing failure in testArchive.

Less ambiguous than previous syntax while keeping names short.
Allows defining more flags without limiting base_category namespace: the
only forbidden base_category id is "related", which was already reserved
(ie, not working) in previous syntax.