I would like to suggest adding version history functionality. This would allow users to track changes made to database entries over time, similar to how page history works in regular Confluence pages.

Use Case
Version history in Confluence databases would be beneficial for several reasons:

1. Accountability: Teams can track who made what changes and when.
2. Error recovery: Users can revert to previous versions if mistakes are made.
3. Change tracking: It becomes easier to see how data has evolved over time.
4. Compliance: For teams that need to maintain audit trails, version history provides a record of all changes.

In our case we use the databases feature for tracking releases of our products. Currently anyone can remove and edit entries in the database.

Implementation Suggestions

1. Add a "History" tab or button to each database entry.
2. Show a list of all changes made to the entry, including the date, time, and user who made the change.
3. Allow users to view the state of the entry at any point in its history.
4. Provide the ability to revert to previous versions if needed.
5. Consider implementing diff views to easily see what changed between versions.

This feature would align well with Confluence's existing version control for pages and would make databases an even more powerful tool for teams to organize and track their work.