noHistory and transaction data

Question

We've got an attribute that we write to fairly often, but don't need history for. While :db:noHistory is clearly the write solution for not logging the history of the data itself, I'm worried that we're also going to accrue a large number of transaction entities as well.

Will that happen? Are transactions still made when the the only datom is for a noHistory attribute? Will we still have database growth issues due to the transactions themselves?

Answer 1

Hi Mitchell,

Yes, the transaction will still be present in the log. The log is a recording of all transaction data in historic order, organized for efficient access. But I would be highly skeptical of this affecting your overall performance/size significantly, and only in reads of the log. Could you help me understand what your underlying concern here is when you say "database growth issues"?

Perhaps it would be useful to have a call to discuss the specifics of your use case. If that's something you'd be interested in I can setup a call with members of our team, just shoot me an e-mail via support@cognitect.com or jaret@cognitect.com.

Cheers!
-Jaret