Entities are not managed by Doctrine

[arcanis]

The main problem is that the fields which are not indexed will not be populated (including non-indexed relations). Of course, it is possible to get 'real' entities after, using their ID, but maybe it would be nice to have a way to do this automagically.

[floriansemm]

This is a good point. I wouldn't do this sync by default, because you can use the annotations for none Doctrine-Entities. It would case an error.

[arcanis]

Maybe something like : ?

$entities = $this->get('solr')->createQuery('AcmeMusicBundle:Track')
    ->useEntityManager($this->getDoctrine()->getEntityManager())
    ->addSearchTerm('name', $keywords)
->getResult();

[floriansemm]

This is a good way. 👍

[rkmax]

I'm having a trouble my postLoad events #67

[vvh-empora]

maybe just throw a hydration event, that will handle the mapping ?

[floriansemm]

@vvh-empora where is your pull request? ;)

What's the best way to reproduce this bug?

[rkmax]

Why not instead of passing the entity manager, it tells hydration strategy like getResult from Doctrine

$entities = $this->get('solr')->createQuery('AcmeMusicBundle:Track')    
    ->addSearchTerm('name', $keywords)
    ->getResult($hydrationMode);

can be:

• SolrQuery::HYDRATE_INDEX
• SolrQuery::HYDRATE_OBJECT

the Entity has the correct entityManager so SolrBundle can should be able to determine which source to use (Index, Odm, ORM, etc)

[floriansemm]

Sounds good for me.

I raised the priority of this issue.

[vvh-empora]

whatever, for my propose, it is nessesary to have control over the hydration. so if you just call the "find" (findOneBy) method it is hard to use the doctrine resultCache. i have define a function like "getById" in my base-repository class, that will handle all the caching features. so, maybe just implement a event for hydration the result and with

$event->stopPropagation();

it is possible to handle the already hydration. of course, you can implement a default hydration handler for the rest of the world, but everyone have a chance to hydrate the result by it own...

[floriansemm]

Sure, I would use a event to pass the information to a dedicated hydration component. Maybe it's possible to use parts of doctrine itself.

I think there are some refactorings in Query/Repository necessary for a clean implementation. (Query needs a dependency to the EventDispatcher, etc.). As part of this its I can imagine to implement a QueryBuilder component. The current query-generation is very simple.

[vvh-empora]

see: #68