#49616 tombstones need not be kept in the entry cache
Opened 2 years ago by lkrispen. Modified 4 months ago

Issue Description

even with a fix for #49615 to get the correct dns for nested tombstones, the incorrect ones are still present in the entry cache.
When an entry is turned into a tombstone we could remove it from the entry cache


Metadata Update from @mreynolds:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 1.3.7.0

2 years ago

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.2 (was: 1.3.7.0)

4 months ago

The tickets #49615, #49616 and #49507 should be handled together, but they didn't get attention for quite some time.
A problem might be that the format changes and we need to be carefule when to introduce it.

Please keep them open and I will look into them again.

Login to comment on this ticket.

Metadata