I'm working on a project that imports contents into Confluence. Since Confluence does not have masquerade feature(well, that's what JIRA ticket from couple of years ago suggested and there's still no update on the ticket.) , I manipulate Confluence Database directly by issuing SQL statements to restore original content creation date, original content creator, likes, and last modified date. To see the changes, I need to flush Confluence Cache and rebuild index. It is not an issue at this point as I'm working on test site. But, soon I'll be working on production site and I'm concern that this may corrupt the database. What should I do to prevent corrupting database?
Your main problems are the caches and index, taking Confluence offline while you run SQL is the only way you can avoid damage to the database. Ideally, avoid SQL like the plague, it's a last resort for working with Confluence (or JIRA)
Hi team, I’m Avinoam, a product manager on Confluence Cloud, and today I’m really excited to let the Community know that all customers can now try out the new editing experience and see some of the ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs