28

I know that Doctrine 2 doesn't support FULLTEXT indexes. I'm actually using a result set mapping and native queries to FULLTEXT search innodb tables (MySQL 5.6). But I still need to mark one or more entity fields as part of the index.

Is there any way to add the index using annotations? It seems that @Index annotation doesn't specify the type of...

gremo
  • 47,186
  • 75
  • 257
  • 421

2 Answers2

60

According to DDC-3014 in the issue tracker of Doctrine, the possibility to specify full-text indices using annotations was implemented on April 14 and will be available in release 2.5. If you don't like to wait, you could try to use the unstable, development version or to backport the commit implementing the feature.

Here is a usage example:

/**
* @Entity
* @Table(indexes={@Index(columns={"content"}, flags={"fulltext"})})
*/
class Comment
{
    /**
    * @Column(type="text")
    */
    private $content;

    ...
}
stollr
  • 6,534
  • 4
  • 43
  • 59
dened
  • 4,253
  • 18
  • 34
  • 2
    Works perfectly with doctrine/orm dev-master, thanks. Unfortunately Doctrine extensions does not work yet with Doctrine 2.5, so I can't use it yet. See this issue (it's about Sylius, but refers to the Tree behaviour with doctrine/orm > 2.4.2): https://github.com/Sylius/Sylius/issues/1325 – gremo Jun 04 '14 at 21:57
3

Here is an example how to make a fulltext index with the yaml mapping driver.

Doctrine\Tests\ORM\Mapping\Comment:
    type: entity
    fields:
        content:
            type: text
    indexes:
        xy_fulltext:
            columns: ["name", "content", "keywords"]
            flags: fulltext