Skip to content

Commit

Permalink
OGM-702 Clarifying semantics of column names used with the Tuple cont…
Browse files Browse the repository at this point in the history
…ract
  • Loading branch information
gunnarmorling committed Jan 6, 2015
1 parent 342bbcf commit 157992e
Showing 1 changed file with 12 additions and 5 deletions.
17 changes: 12 additions & 5 deletions core/src/main/java/org/hibernate/ogm/model/spi/TupleSnapshot.java
Original file line number Diff line number Diff line change
Expand Up @@ -9,11 +9,18 @@
import java.util.Set;

/**
* Represents the Tuple snapshot as loaded by the datastore.
* Interface implemented by the datastore dialect to avoid data
* duplication in memory (if possible).
*
* Note that this snapshot will not be modified by the Hibernate OGM engine
* Represents a tuple snapshot as loaded by the datastore.
* <p>
* This interface is to be implemented by dialects to avoid data duplication in memory (if possible), typically wrapping
* a store-specific representation of the tuple data. This snapshot will never be modified by the Hibernate OGM engine.
* <p>
* Note that in the case of embeddables (e.g. composite ids), column names are given using dot notation, e.g.
* "id.countryCode" or "address.city.zipCode". The column names of the physical JPA model will be used, as e.g. given
* via {@code @Column} .
* <p>
* In some special cases implementations may chose to persist different names than mandated by this model, e.g. always
* {@code _id} will be used as id column name by MongoDB. It is the responsibility of such implementation in this case
* to do the required translation of column names internally.
*
* @author Emmanuel Bernard &lt;emmanuel@hibernate.org&gt;
*/
Expand Down

0 comments on commit 157992e

Please sign in to comment.