Changes between Version 25 and Version 26 of GenericTrac

Timestamp:

Jul 14, 2010, 9:00:13 AM (14 years ago)

Author:

Christian Boos

Comment:

Note about possible future directions - RDBMS are not the only alternatives

GenericTrac

@@ -42 +42 @@
  4. it should lead to a more ''compact'' representation of data
  5. all the existing constraints about maintaining resource history and associated metadata should be taken into account
+
+Note that the persistence constraints imposed by the Trac data model are not necessarily only (or even best) approached using the RelationalModel, one could imagine that a future version could use more document-oriented persistence layers (e.g. [http://www.mongodb.org/ MongoDB]), or object-oriented databases (e.g. [http://www.zodb.org/ ZODB]). Alternatively, the versioning of resources could be delegated to a version control backend, and even a [DistributedTrac distributed] one.
 
 === Resource Content ===