* to quickly setup catalog_full_text table, you can use the following SQL.

  REPLACE INTO catalog_full_text SELECT uid, title, description FROM catalog;

* non fulltext queries like '=abc', '>abc', '%abc%' are supported.

* now erp5_full_text_mroonga_catalog is used for unit tests thus I recommend using it instead of erp5_full_text_myisam_catalog.

* to migrate existing MyISAM full_text table into Mroonga, you can use the following SQL.

  ALTER TABLE full_text DROP KEY SearchableText,
    ENGINE = mroonga,
    ADD FULLTEXT KEY SearchableText (`SearchableText`) COMMENT 'parser "TokenBigramSplitSymbolAlpha"';

* fulltext search score is no longer provided as (column_name) but now provided as (column_name)__score__.

* (category)_title, like source_title, related keys are automatically generated. (category)_description keys as well.

syncml : fix method-id that indexed data in the after_method_id so that order of synchronization is followed

Also simplify a bit the code

- do not use getToolByName.
- do not put two statements on the same line
- merge nested "if" statements around a single code block

Amend 9240d498: Since many Loaders are
instanciated by unittest itself, filter_test_list still have to be a class
variable

This reverts commit 15aaafbf.
Reason: To be consistent with packing list and order until
the new way of handling payment conditions is implemented.

  This parameter has been passed always by the erp5.util implementation. Introduce
  this parameter makes the API compatible for future implementation with support
  to scalability tests even if the current code is not ready yet.

A simpler way to achieve the same fix.