http://www.doctrine-project.org/jira This file is an XML representation of an issue en-us 5.2.7 850 21-02-2013 http://www.doctrine-project.org/jira/browse/PHPCR-84 Doctrine PHPCR <p>when searching there must be some way to ensure that for translateable documents the right fields are filters. f.e. when using the child strategy then for the given columns the node name needs to be checked (nodename = phpcr_locale:fr). for attributes strategy the property name needs to be rewritten ("title" vs "phpcr_locale:fr-title").</p> <p>it might not be possible to easily automate this.</p> PHPCR-84

make the query API work with i18n

Bug Blocker Open Unresolved Lukas Kahwe Lukas Kahwe Tue, 23 Oct 2012 21:17:33 +0000 Tue, 14 May 2013 07:07:33 +0000 0 3 <p>sounds like asking for a PHPCR-ODM DQL , then we could handle this perfectly transparent. as an intermediate, a method to build the criterion for a field of a mapped entity would be the right way i think. you could even do that for non-multilang in case you mapped the documents field to some differently named PHPCR property.</p> <p>here is an example where i manually handle this:<br/> <a href="https://github.com/symfony-cmf/SearchBundle/blob/master/Controller/PhpcrSearchController.php" class="external-link">https://github.com/symfony-cmf/SearchBundle/blob/master/Controller/PhpcrSearchController.php</a></p> <p>if we were to do it automatically we might not need our own DQL, we could do a QOMWalker. however i doubt that we can fully automate this, since everything can be mixed. ie. one path can have any number of different strategies.</p> <p>btw .. it might make sense to always namespace the property names, even when using the child translation strategy. this could make it easier to deal with searching across mixed translation strategies.</p> <p>if we do this change we should provide a migration script</p> <p>it gets even worse when translated and non-translated documents get mixed up. see for example the cmf sandbox menu admin (not multilang menu). it mixes translated and non-translated documents. since <a href="https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/pull/100" class="external-link">https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/pull/100</a> you can sort on columns, so sorting will half work half not.</p> <p>there seem to be other solutions like descendant, but if we had <b>join</b> in jackalope-doctrine-dbal that could be a good option <a href="https://github.com/jackalope/jackalope-doctrine-dbal/issues/15" class="external-link">https://github.com/jackalope/jackalope-doctrine-dbal/issues/15</a></p> <p>I started working on the Join issue and will start working on this issue when the Join feature is more or less stable.</p>