3 ms·
You can have a design where your previous version of a record gets automatically copied into another table along with the timestamp of the operation. Then you c
by alexro 15y ago
You can have a design where your previous version of a record gets automatically copied into another table along with the timestamp of the operation. Then you can slice this history however you want. All with no additional app code.
But I wouldn't write off the noDB approach for various transitional data, or data that isn't mean to live long anyway, like tweets.
- enjo 15y agoWhy would the lifetime of the data be at all relevant? Most noDB (a term I don't like much) stores are built to be highly durable. There are a lot of questions that make the choice of data store a difficult one, but I'm not sure that plays into it at all.