Home » Support » Issue Tracking » Best practice for history tracking

Best practice for history tracking

Type: Feature requestVersion: 1.4.0Priority: NormalStatus: ClosedReplies: 1
#1

We would like to add to records start and end timestamp fields. When end field is null, it indicates the last version of this item.

Few questions:

  • in terms of performance, what would be faster, having a single timestamp and looking for the top1 when ordered by time or the above solution, looking for null end field?
  • If using end field, would an index matter?
  • what is the best way to intercept the update operation, clone the object, update the old one (if end field is used) and save the clone object as new?
  • What is the recommended way for creating a UUID PK?

Avishay Ben Natan

#2

Could you please post the questions again to the ObjectDB forum?

The issue tracking is only for reporting bugs and feature requests and not for general discussion and questions.

In addition, every post should discuss one topic, so I think it would be better to separate the last question about UUID PK and post it as a separate thread.

These questions are of great value for other users so it is important that it would be easy for others to find and see the questions and the answers.

Thanks!

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)

Post Reply

To post a reply and/or subscribe to update notifications - please login