Spring Persistence Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
=Repository= | =Repository= | ||
Any repository implementation needs access to a persistence resource, depending on the persistence technology used. For example, a JDBC-based repository needs access to a [[DataSource#Overview|JDBC DataSource]], while a JPA-based repository needs access to an EntityManager. | Any repository implementation needs access to a persistence resource, depending on the persistence technology used. For example, a JDBC-based repository needs access to a [[DataSource#Overview|JDBC DataSource]], while a JPA-based repository needs access to an [[JPA Concepts#EntityManager|EntityManager]]. | ||
[[@Repository]] | [[@Repository]] | ||
Revision as of 20:34, 14 October 2018
Internal
Overview
DAO
Repository
Any repository implementation needs access to a persistence resource, depending on the persistence technology used. For example, a JDBC-based repository needs access to a JDBC DataSource, while a JPA-based repository needs access to an EntityManager.
Object IDs
- When persisting objects in a relational database, it is generally a good idea to have one field in the object that uniquely identifies the object. See Relational Databases.