Atlassian Database Page Types and Version Control History

[Jack Kiron]

Hello,

I've recently started using the database page types for publishing information in my dev team. This page type has made some items easier to visualize and track. However, a downside I believe to have noticed is there is not a way for version control in the databases. Is there not backups kept of these pages like a normal wiki (e.g page history)? I understand this goes against the methodology of database systems. Although having a feature like this would be ideal for keeping accidental deletions or updates by users reversable. Is this already a feature or are their plans to add this. A feature to backup every night or after large changes have been made to protect the tables from team members accidents. Thanks.

[Kristian Klima]

Hi @Jack Kiron and welcome to the Community.

Databases have no version control :(

What you can do is export a DB manually every day and keep the track in another tool.

[Jack Kiron]

Hi Kristian thanks for your speedy reply!

That's a bummer to hear... when making updates to DB's using SQL for example, you're aware of the consequences behind each potential statement. Does Atlassian have any automation in place for saving DB page types? Perhaps something that adds a table to the same page that's locked by owner of that page? Using them similarly to a failover? I'd rather not have to increase daily tasks if at all possible where automation is possible. If there's nothing available right now I'll bite the bullet I suppose and just do it manually as you recommended. Probably also inform my team of the difficulties that can be caused if not cautious. Unfortunately, this also means I will be far more hesitant to use this page type in the future because no one is safe from human errors. I don't suppose there's a way to have this feature as a request for databases? I have never used atlassian forums for support before but would love to have this requested as a proposed feature.

[Kristian Klima]

It seems that the only DB related automation is 'Database Created'

But I wonder if you can turn this around, basically use your DB as a (mostly) passive DB and create values elsewhere. In other words, you'd outsource version control elsewhere and use your DB only to display stuff.

For example, I'm using a DB as one of the docs life-cycle management tool (more here). Everything in that DB is auto generated from the main entry - a page.

Yes, I have to add a page manually but all other columns are populated manually.