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

In older ZSQLCatalog versions (pre-r25706), values fetched via
  select_expression='catalog.simulation_state'
were accessible on brain as "brain.simulation_state". In current catalog,
this became "getattr(brain, 'catalog.simulation_state')" and hence broke
compatibility somewhat. This patch fixes this problem by stripping table
name from the generated alias.
Note: the table name is only stripped from implicit aliases, never from
explicit ones.


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

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

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

Fulltext operator (MatchComparisonOperator) is special because it generates
ORDER BY expression, which is to be used only if caller tells catalog to sort
on the fulltext column. This code tests just that.


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

As the generated order-by expressions now (rightly) differ based on data, the
exception generated when detecting the difference must be postponed to when
expression is actualy used, as it might not be used.
Also, test that postponing effectively works, and demonstrate another way to
express the same condition, but which allows sorting.


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

  either on the brain or on the real object
* update unit test for getProperty
* add new method hasColumn in catalog API
* add test for hasColumn

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

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

That was category relation related.

Lazy generation of category relation is replaced by using
IN with sub query.


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

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

Add one more select_dict case: when there is no direct hint given, but the query implicitely favors a table over the other.


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

- add a column which mapping is ambiguous (could happen on 2 tables)
- add a utility method to generate SQLExpression instances from parameters


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

expressions


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

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

This fix makes search dialogs work even if datetime field is included.


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

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

Add a test.
FullText operators have no SearchText representation, so disable it explicitely.


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

Improve usability of SimpleQuery when directly instanciated: automaticaly convert an "=" comparison operator on a None value into an "is" comparison operator.
Update code comment, as it is not about backward compatibility but about usability.
Add a test.


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

When doing multiple FullText lookups in the same SearchText expression, merge all lookups into just one SQL fulltext match (per expression block).
Add a test.


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

Export isAdvancedSearchText method on SQLCatalog instance.
Document SQLCatalog.isAdvancedSearchText in IQueryCatalog interface.
Add a test for new SQLCatalog.isAdvancedSearchText method.


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

Update test to new desired behaviour.


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

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

Modify SimpleQuery API to deprecate "operator" parameter in favor of "comparison_operator". Preserve backward compatibility.
Update all callers.


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

Fix SearchText parsing: it was not passing desired logical_operator to buildQuery, causing AND to becore OR (only for logical operator syntax tree node directly containing leaf nodes).


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

Make "from string import split" unused in SQLCatalog, and remove string import entirely.


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

Split test_001_DefaultKey, test_003_DateTimeKey and test_004_KeywordKey into 2 tests each, instead of using a 2-items loop in each.


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

Enable parsing in DefaultKey. Update test to describe that behaviour (which is more consistent with previous behaviour).


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

Generate automaticaly "not like" operator use in KeywordKey when given operator is "!=" and value contains at least one "%".
Update test to chekc for "not like" operator.


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

Remove testSearchKeys.


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

  A "ScriptableKey" configuration is not a SearchKey, strictly speaking: a
  SearchKey generates Query instances from a value (the SearchKey contains the
  column information), and ScriptableKey's "script" does exactly that. So
  there is no need for any SearchKey to generate those Queries, so it's better
  to fix the feature at getColumnDefaultSearchKey caller's level.


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

- further extend SearchKey concept
- define, implement and validate Interfaces
- add a column mapper (mapping is decided on a completely-formed query tree instead of being done individualy on each used column)
- state what is present for backward compatibility, warn about deprecated/dangerous uses


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