I have a legacy application that was using Xaraya to manage user content 
that I am trying to replace with a rewrite using Symfony/Sonata to manage 
users and/or content.

For whatever reason, previous developers managed this with two different 
databases (MySQL for Xaraya, and SQL Server for other things, including 
authenticating users).

I am trying to create Entity mappings such that the users/groups from 
SonataUserBundle (which extends FOSUserBundle) use the entity manager 
associated with the login database connection, and this works for logging 
into the admin site itself, but blows up when it tries to hydrate objects 
that have associations to the User entity.

It appears that Doctrine does not try to find the entity manager associated 
with an entity when hydrating an object's associations.

My question is this: it it possible to make Doctrine hydrate objects using 
the entity manager for an entity instead of assuming it's mapped to the 
current entity manager, and if not, is there any form of a clean code 
work-around for it?

Thanks.

(Note: The method of using the "databasename.tablename" syntax in the query 
that I have seen mentioned elsewhere will not work for my use case.)

-- 
You received this message because you are subscribed to the Google Groups 
"doctrine-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to