StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16610784
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-05-17T13:52:26.573
FavoriteCount
0
LastActivityDate
2013-05-17T16:30:30.280
LastEditDate
2013-05-17T16:30:30.280
LastEditorUserId
666906
OwnerUserId
666906
ParentId
16550086
PostTypeId
2
Score
13
ViewCount
0
LastEditorDisplayName
text
Body
There is no magic under the hood. <pre><code><jpa:repositories base-package="com.foo.repos.ora" entity-manager-factory-ref="entityManagerFactory"/> </code></pre> doesn't help you at all with your custom interface implementations. Best way I found is to treat your custom implementations as regular beans. So I defined a 'sharedEntitManager' bean in my spring configuration like so <pre><code><bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"> ... </bean> <bean id="sharedEntityManager" class="org.springframework.orm.jpa.support.SharedEntityManagerBean"> <property name = "entityManagerFactory" ref="entityManagerFactory"/> </bean> </code></pre> After that, I simply injected the EntityManager into my implementation beans <pre><code><bean id="aRepositoryImpl" class="comm.foo.repos.ora.ARepositoryImpl"> <property name="entityManager" ref="sharedEntityManager"/> </bean> </code></pre> The 'entity-manager-factory-ref' attribute discriminates between different entitymanager factories but only for straight Spring Data Repositories (i.e. only for interfaces). It doesn't however concern itself with any of your implementations. To sum it up 1) if you simply rely on standard Spring Data repositories with no custom implementation, use the "entity-manager-factory-ref" attribute to differentiate databases. 2a) Additionally, if you use any custom implementation, inject the appropriate EntityManager directly into the implementing class. Wirering is done under control of your spring xml configuration. For some reason I wasn't able to use the @Autowire annotation with a @Qualifier to reference the correct EntityManager. EDIT I just learned about the <a href="http://forum.springsource.org/showthread.php?60659-Problem-with-Autowired-%28requires-Qualifier%29&p=203095#post203095">@Resource</a> annotation <pre><code>@Resource(name = "sharedEntityManagerA") EntityManager entityManager <bean id="sharedEntityManagerA" name="sharedEntityManagerA" class="org.springframework.orm.jpa.support.SharedEntityManagerBean"> <property name = "entityManagerFactory" ref="entityManagerFactory"/> </bean> </code></pre> With this at hand selecting what EntityMAnger should be used becomes straightforward. No need of plumbing everything togehther in your context xml. 2b) As an alternative to Spring's xml configuration for hooking up your stuff you may also go with <blockquote> @PersistenceContext( unitName = "nameOfPersistenceUnit" ) </blockquote> to inject the correct EntitymanagerFactory While 'nameOfPersistenceUnit' referes to your persistence sitting in your standard JPA persistence.xml However 2b) doesn't go well with 'QueryDslRepositorySupport', since it expects an EntityManager instance. But I found that 'QueryDslRepositorySupport' doesn't offer much support anyway, so I removed it.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSpring Data JPA: Repositories for multiple database / Entitymanger configurations
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USsimou
UserOwnerUserId
1. USsimou
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. CO2b) also works like a charm if you have two `LocalContainerEntityManagerFactoryBean`s in your application context, each with their own `persistenceUnitName`.
 singulars
 PostPostId
 PO
 UserUserId
 USEmil Lundberg

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.