FULLTEXT search problem

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • diyoyo
    Member
    • Jul 2018
    • 88
    #1

    FULLTEXT search problem

    Hi,
    it seems that there is a bug when adding new fields to the fulltext indexing of an entity.
    In fact, I noticed that whenever the field was encoded as "utf8mb4_unicode_ci", EspoCRM failed rebuilding.
    However, if everything is "utf8_unicode_ci", then I am able to add as many FULLTEXT indices as I want.

    I am using MariaDB 10, php 5.6

    Thanks.
    Tags: None
    • yuri
      Member
      • Mar 2014
      • 8440
      #2
      Hi,

      Please check this link: https://forum.espocrm.com/forum/bug-...o-report-a-bug

      If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

        Comment

        • yuri
          Member
          • Mar 2014
          • 8440
          #3
          What's in log?

          We officially don't support MariaDB, nevertheless we tested fulltext there and it worked.
          If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

            Comment

            • diyoyo
              Member
              • Jul 2018
              • 88
              #4
              Rebuild database fault: exception 'PDOException' with message 'SQLSTATE[HY000]: General error: 1283 Column 'description' cannot be part of FULLTEXT index
              Well, it works, but only after going to phpmyadmin to change the encoding of the specific field, which was created automatically as "utf8mb4_unicode_ci".

              Basically, if that helps, even when trying to add the index manually within phpMyAdmin interface, it actually replaces the default fulltext index (on "name"), except if I switch back to "utf8_unicode_ci" encoding.

                Comment

                • yuri
                  Member
                  • Mar 2014
                  • 8440
                  #5
                  I highly recommend using utf8mb4_unicode_ci for text/varchar fields.


                  Do you have only one field in text filters?
                  If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

                    Comment

                    • diyoyo
                      Member
                      • Jul 2018
                      • 88
                      #6
                      ... And now, it works fine on other entities, without changing anything :s ...

                      To answer your question: by default yes: name, and then I want to add more fields, like description and more.

                      I have to dig deeper into how to reproduce this, because now everything seems to be fine.

                        Comment

                        Previous template Next
                        Working...