Author: buildbot
Date: Fri Jun 13 15:10:23 2014
New Revision: 912453
Log:
Staging update by buildbot for gora
Modified:
websites/staging/gora/trunk/content/ (props changed)
websites/staging/gora/trunk/content/current/tutorial.html
Propchange: websites/staging/gora/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jun 13 15:10:23 2014
@@ -1 +1 @@
-1601870
+1602457
Modified: websites/staging/gora/trunk/content/current/tutorial.html
==============================================================================
--- websites/staging/gora/trunk/content/current/tutorial.html (original)
+++ websites/staging/gora/trunk/content/current/tutorial.html Fri Jun 13
15:10:23 2014
@@ -175,7 +175,7 @@ analyzing the data with extensive Apache
beans to hold the data and RPC interfaces are defined using a JSON
schema. In mapping the data beans to data store specific settings,
Gora depends on mapping files, which are specific to each data store.
-Unlike other ORM implementations, Gora the data bean to data store
+Unlike other OTD (Object-to-Datastore) mapping implementations in Gora the
data bean to data store
specific schema mapping is explicit. This has the advantage that,
when using data models such as HBase and Cassandra, you can always
know how the values are persisted.</p>
