[binarycloud-cvs-commit] cvs: r2 /binarycloud/docs/specs/xml EntityDefinition.php.xml

[alex <bin...@li...>]

alex		Sat Oct  6 19:09:55 2001 EDT

  Modified files:              
    /r2/binarycloud/docs/specs/xml	EntityDefinition.php.xml 
  Log:
  Added entity:history and an explanation.
  
  
Index: r2/binarycloud/docs/specs/xml/EntityDefinition.php.xml
diff -u r2/binarycloud/docs/specs/xml/EntityDefinition.php.xml:1.3 r2/binarycloud/docs/specs/xml/EntityDefinition.php.xml:1.4
--- r2/binarycloud/docs/specs/xml/EntityDefinition.php.xml:1.3	Tue Sep 25 13:01:19 2001
+++ r2/binarycloud/docs/specs/xml/EntityDefinition.php.xml	Sat Oct  6 19:09:54 2001
@@ -1,5 +1,6 @@
 <entity>
-<!-- this is a temp storage site for these notes:
+<!--
+this is a temp storage site for these notes:
 For modules to be distributed with binarycloud or available
 from the (upcoming) module repository, as well as for
 binarycloud core components you must:
@@ -27,6 +28,25 @@
 	a class.
 	-->
 	<entity:manager>FurbeesManager<entity:manager>
+
+	<!--
+	whether to maintain a history of records for this entity.
+	so:
+    -When you generate metabase xml schemas, _two_ schemas
+    would be created, one with the name of the entity:
+    "furbees" and another: "furbees_history"
+
+    -furbees_history would contain the same fields as
+    furbees, with the addition of two important fields:
+        -history_id
+        -history_timestamp
+
+    With those two tables, it would be _relatively_
+    easy to implement a GetByHistory() method in EntityManager,
+    which would trickle down to the correct Query to
+    furbees_history through QueryManager..
+	-->	
+	<entity:history>true</entity:history>
 	
 	<!--
 	db-related stuff for compatibility with metabase.