Tutorial is available at http://www.erp5.com/P-OSOE-R.Order.Prediction.

This will prevent cache manifest update issue.

Update callers which could not be fixed so they disable the exception.
Reviewed-by: Jerôme Perrin <jerome@nexedi.com>

Reviewed-by: Jerôme Perrin <jerome@nexedi.com>

In the same time, remove checking of legacy business template, they
are not maintained any more.

Do not check naming conventions for field libraries in many business
templates that would need cleanup first (the list is harcoded, this
way any new bt will be checked automatically)

Otherwise we quickly end up with thousands of activities when one builder has a problem.

When testnodes are unable to create partitions and unable to find
runTestSuite command, this change avoid having the testnode always
trying to reuse same revision by forcing to move test result to failed

Disable stock cache by removing erp5_syock_cache from skin selection.

- Dates Are now using ISOString providing efficient sorting as string
- modification_date property is not saved on object
- Modified conflict_handling parameter to overwrite the remote document with local content (no loss of data)
- the three different storage use different local databases

This caching policy should be the default for any offline webapp, to prevent any mistake done with the html5 cache manifest.

This reapplies commit 648d7020

Also enable pretty printing of kw and activity_kw

* Use editable fields with `pre` style for listbox columns
* Display h:m along with start date

Also fix a naming issue with one field

When searching accounts by validation state, the stat of number of movements on an account could be wrong

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>

Now you can sort results by full text search score, for example.

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