compactDatafile remove ttl index configuration from datastore file

[andrea-tomassi]

Bug Report: TTL Index Information Lost After compactDatafile Function Call

Description

When the compactDatafile function is called on a datastore that has a TTL index, the information related to the TTL index is deleted. This means that any automatic deletion of documents based on the TTL index will no longer occur after the compaction.

To Reproduce

1. Create a NeDB datastore and add a TTL index to it.
2. Insert some documents that should be affected by the TTL index.
3. Call the compactDatafile function on the datastore.
4. Observe that the TTL index information is lost, and documents are no longer automatically deleted based on the TTL.

Expected Behavior

The expected behavior is that after calling compactDatafile, the TTL index should remain intact, and documents should continue to be automatically deleted according to the TTL settings.

Actual Behavior

The actual behavior is that the TTL index information is deleted, and documents are no longer automatically deleted based on the TTL.

Logs

Logs would typically show the compaction process but might not explicitly indicate the deletion of the TTL index information unless additional logging is added.

Environment Info

• Runtime: Node 20
• NeDB Version: 4.0.4
• OS: Kubernetes Pod