Announcement

Collapse
No announcement yet.

Rebuild database fault: Column 'name' cannot be part of FULLTEXT index in...

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Rebuild database fault: Column 'name' cannot be part of FULLTEXT index in...

    Espo.ALERT: Rebuild database fault: PDOException: SQLSTATE[HY000]: General error: 1283 Column 'name' cannot be part of FULLTEXT index in...
    For one reason or the other, I was unable to REBUILD the database. Only after seeing the logfile and removing the NAMEfield from the 'Text Filter Fields' I am able to REBUILD again. Adding the NAMEfield to the 'Text Filter Fields' gives a 500 error on the frontpage while REBUILDING. (NAMEfield is a VARCHAR of 249 characters...so should be ok) I had this issue with 5.6.14, thought I would upgrade to 5.7.5, but error is still there... Maybe it has something to do with ISSUE #1470 ??

  • #2
    Hello Bill,
    please try to add the 'name' field back to the 'Text Filter Fields' and make the rebuild from CLI
    Code:
    php rebuild.php

    Comment


    • #3
      Originally posted by Maximus View Post
      Hello Bill,
      please try to add the 'name' field back to the 'Text Filter Fields' and make the rebuild from CLI
      Code:
      php rebuild.php
      Thanks... did not work. But I just found out what works: 'Full-Text Search' option was on, have turned off and now the rebuilding works... But of course 'Full-Text Search' does not work anymore...

      Comment


      • #4
        Could you tell me where the full-text search was enabled (what entity) end what fields were added to its scope? I will try to reproduce.

        Comment


        • #5
          Originally posted by Maximus View Post
          Could you tell me where the full-text search was enabled (what entity) end what fields were added to its scope? I will try to reproduce.
          yes, Go to ENTITY MANAGER. Then EDIT ACCOUNT. Here you can select FULL TEXT SEARCH

          Comment


          • #6
            After the successful upgrade, did you try to enable Full-text search and test it?

            Comment


            • #7
              Just tested it with version 5.7.6 but the problem is still there...

              Comment

              Working...
              X