You need to capture last update time yourself. For my application, I keep an AuditTrail object, which captures AuditEvents. These events occur on any insert, update, or delete of an object (delete is virtual in my system, just setting a flag). For each AuditEvent, I keep track of the date, authenticated user, db action, and … Read more
You can use any type of value for an _id field (except for Arrays). If you choose not to use ObjectId, you’ll have to somehow guarantee uniqueness of values (casting ObjectId to string will do). If you try to insert duplicate key, error will occur and you’ll have to deal with it. I’m not sure … Read more
In my latest iteration on an existing system using Spring and Hibernate, I have started to move in a similar matter. When first implementing Hibernate models, I strove to separate the application logic in service classes from the persistence logic via data access objects. When building a new system last year I allowed most of … Read more
You can use objects for the _id field as well. The _id field is always unique. That way you kind of get a composite primary key: { _id : { a : 1, b: 1} } Just be careful when creating these ids that the order of keys (a and b in the example) matters, … Read more
Technically tests that talk to a database (nosql or otherwise) are not unit tests, as the tests are testing interactions with an external system, and not just testing an isolated unit of code. However tests that talk to a database are often extremely useful, and are often fast enough to run with the other unit … Read more