[Neos] Content Repository Search without dependencies

Christian Müller christian.mueller at typo3.org
Mon Apr 21 15:30:31 CEST 2014

Dominique Feyer wrote:
> Why not a simple flat index in MySQL ? With a table like nodeIdentifier, propertyName, propertyValue (maybe multiple propertyValueString, propertyValueInterger, … to optimize index usage in MySQL) ?
Yes thought about that too. The problem is sorting performance then. And 
fulltext search. But I certainly will try/implement that as well.

> The problem with Sqllite, is the scalability, as soon as we need a multiple server, this solution will not be usable.
Sure, but I would consider a multi server environment not the target of 
this solution. If you need that you should rather use ElasticSearch IMHO.

> We definitively need a solution, and as any TYPO3CR installation use MySQL or Postgres, why not using this technologies for the default search implementation ?
Doctrine is too abstracted to get good performance in this. You would 
rather want to use specific implementation abilities like fulltext index 
of MySQL. I think that quickly becomes tedious to implement but I guess 
I will implement a MySQL solution as well at some point.

> How the PHPCR implement search fonctionnalities ?
Will investigate that.


More information about the Neos mailing list