Support Forums: Message List - Patterns for versioning database entities?

more comments

Sat, 11 Sep 2004 21:12:29 -0400

In terms of scalability I have not used JDO (the KODO implementation for
more than a few thousand rows. However, this would really depend on the JDO
vendor.

In terms of your point 1) I do not think this is viable under a relatrional model....

some thoughts

Fri, 10 Sep 2004 08:52:09 -0400

Interesting, bruce. How scalable have you found JDO to be, BTW?

In terms of links, I have used two solutions:

1. reference version of an entity

2. reference a specific version of an entity.

With (1) your links...

some thoughts

Thu, 09 Sep 2004 18:00:39 -0400

I do something very similar. I use JDO for persistence for use the following
patterns:

1. Every table has a version number and a parent id (which is similir to your solution).
2. A use a mini-rules engine to allow for "callbacks"...

Patterns for versioning database entities?

Thu, 09 Sep 2004 08:08:57 -0400

I have worked on several applications that required full versioning of all database entities, not just to meet audit log requirements but so that older versions of entities can be viewed at any point. Often this is required for a document-based workflow...