Changes between Version 5 and Version 6 of Backtracking

Timestamp:

Oct 16, 2009, 3:13:56 PM (15 years ago)

Author:

jurzua

Comment:

--

Backtracking

@@ -25 +25 @@
 The attribute systemStatus is not useful to build the a version of an entity, because every entity's versions will have the same value. The attribute unique for each version is the modifier, therefore the query will look like this:
 
-  ''select * from entity, attribute,  entity_attribute where entity.id = X && attribute.id= Y &&  entity_attribute.entityId = X && entity_attribute.attributeId= Y && entity. modifier = Z && attribute. modifier = Z'', where X and Y are numbers and Z is a time stamp.
+  
+{{{
+select * from entity, attribute,  entity_attribute where entity.id = X && attribute.id= Y &&  entity_attribute.entityId = X && entity_attribute.attributeId= Y && entity. modifier = Z && attribute. modifier = Z
+}}}
+, where X and Y are numbers and Z is a time stamp.
 
 '''Analysis of Behavior'''
@@ -34 +38 @@
 Attribute[id:2, systemStatus:original, modifier:x]  
 
-* Modification of an Entity
+* '''Modification of an Entity'''
+
 A modification on an Entity will create a copy of the edited entity and its corresponding attributes (and relations). The new copy will have the value “original” in systemStatus and the current time in modifier. In the old version will be change only the attribute systemStatus from “original to copy”.
 
@@ -45 +50 @@
 Both the table entity_attribute and the table_relation should not be changed.
 
-* Elimination of an Attribute
+* '''Elimination of an Attribute'''
+
 An elimination of an attribute will mean the following changes:
 
@@ -55 +61 @@
 For this case both the table entity_attribute and the table_relation should not be changed, because the reference between the attribute and the entity is used by the previous versions.
 
-* Insertion of an Attribute
+* '''Insertion of an Attribute'''
+
 An insertion of an attribute will mean the following changes: