Make the removal of non-versionable content items hard deletes

[pgy866]

Delete the published content entries, the database still save the data, delete content is not synchronized. 删除发布的内容条目，数据库内依旧保存数据，不同步删除内容。

Do not know, is this design, or wrong? 不知道是不是就是这样设计的，还是一个错误呢？

Can provide an action UI to completely delete deleted content? Keep clean database files. 可以提供彻底删除已删除内容的操作UI吗？保留干净的数据库文件。

[sebastienros]

This is intentional, these are soft deletes. The records are kept but flagged as deleted, to preserve history. In the future we'll have a module to prune this data.

[EternityTeam]

@sebastienros Has this module been completed? In the latest development version, I found that logical deletion is still the default.

[sebastienros]

No, there is no such module. But I think there is an option on the content type to make the items non-versionable, in which case it won't store the previous versions.

[EternityTeam]

@sebastienros Yes, when I turn off the versionable option for content types, it does not generate multiple historical records after many modifications, but when I delete this content item, it sets the values of Latest and Published fields of the ContentItemIndex table to zero and the Id field gets a new value without deleting the index record, and the record in the Document table still exists.

I had delete the content item from UI，but...

[sebastienros]

Maybe an issue, if a content item is not versionable and deleted we could get rid of it.