1. 15 Jul, 2016 4 commits
  2. 23 Jun, 2016 1 commit
  3. 13 Jun, 2016 2 commits
  4. 24 May, 2016 1 commit
  5. 10 May, 2016 1 commit
  6. 04 May, 2016 1 commit
  7. 21 Apr, 2016 1 commit
  8. 15 Apr, 2016 1 commit
  9. 04 Apr, 2016 2 commits
  10. 12 Jan, 2016 3 commits
  11. 25 Nov, 2015 1 commit
  12. 19 Oct, 2015 2 commits
  13. 07 Oct, 2015 5 commits
  14. 04 Oct, 2015 1 commit
    • Kazuhiko Shiozaki's avatar
      Add auto_extend_select_list argument in buildSQLQuery() and use alias in... · bdcdaca8
      Kazuhiko Shiozaki authored
      Add auto_extend_select_list argument in buildSQLQuery() and use alias in group_by_expression and order_by_expression.
      
      If True, select_list is automatically extended to have columns used in
      group_by_list and order_by_list. It is useful when use
      select_expression in inner query and use group_by_expression or
      order_by_expression in outer query.
      bdcdaca8
  15. 24 Sep, 2015 2 commits
  16. 22 Sep, 2015 1 commit
  17. 18 Sep, 2015 2 commits
  18. 14 Aug, 2015 3 commits
  19. 10 Jul, 2015 1 commit
    • Vincent Pelletier's avatar
      EP5Type.Utils: Update SQL escaping rules. · 39c4873a
      Vincent Pelletier authored
      Sadly, we still implement our own escaping, as places escaping strings do
      not know which connector will be used (proper escaping is
      connector-dependent, because database-dependent).
      Move this method in ZSQLCatalog to factorise code.
      39c4873a
  20. 17 Mar, 2015 1 commit
  21. 19 Nov, 2014 2 commits
  22. 18 Nov, 2014 1 commit
  23. 08 Nov, 2014 1 commit
    • Kazuhiko Shiozaki's avatar
      use fulltext search in title and description. · d47df833
      Kazuhiko Shiozaki authored
      * 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.
      d47df833