Reconnect to database that already exists

This is a feature request as well as a "how in the world do I do this?" question.

I have a QNAP running my postgres in Container Station. Ugh, I know. But that's what the tutorials suggested, so I followed them. It's been working great. But I rewired, things got weird, and I disconnected from the database in an attempt to fix everything.

Turns out that is a huge mistake because Resolve does not allow you to reconnect to a postgres database the way it does with local ones. Apparently, it merely spits out an error saying that the database already exists. What I would prefer is a huge button that says, "Would you like to reconnect to this database because why else would you be typing this information into the fields here?" ... or, more simply, "Reconnect".

Like so:

reconnect.png (8.59 KiB) Viewed 2417 times

Since that button does not exist ... what do I do? I searched the forums and the manual and all I've seen is use the Project Server application and manually drag the file over. But since this is a database in Container Station, I can't find it in my Explorer file structure, and I don't have the server application installed because I've never needed it.

Do I install the new Davinci Resolve Project Server application from support? Will that help me at all? I'm skeptical since it's not the Studio version, which I am running, which has all those features built in (specs in signature for WORK machine).

So confused right now.

Thanks for your help!

~Luke

[Dwaine Maggart]

There is no issue if you disconnect a PostgreSQL database, and then want to Connect to it again, as long as nothing else has changed.

In Resolve 17, the Connect icon is now at the top of the Database area of the Project Manager page, next to the Backup and Restore icons. This is new in 17.

If you select that Connect icon, and enter the name of the database you disconnected from, it should connect. If it doesn't, then it would seem like you didn't really disconnect from it previously.

If you RESTORE a database BACKUP, then you have to use a new database name. You can't restore a backup to an existing db. So if you have a backup of database fred, and you want to restore it, you can't restore it to fred. You'd need to restore it to fred2, or some other new name.

If you still have issues, send a Resolve log file (Resolve Help menu: Create Diagnostics Log on Desktop) and the name of the database you are trying to connect to. Generate the log immediately after trying to connect to the db and getting the error message.

So if you have a backup of database fred, and you want to restore it, you can't restore it to fred. You'd need to restore it to fred2, or some other new name.

What if you're on a new machine, which doesn't currently have a fred database?

[Dwaine Maggart]

Then you can use any name you want, including fred.

I think the issue is much simpler and confused a lot of users moving to dr17.
There is now a dedicated little icon to reconnect an existing postgresql database . So different then before where it was located in the same tab as to create a new database.
Typing on a mobile so cant post the image now but have a look. There is a small icon there on the top of the left column where you see all your available databases that does the job

Thanks Dwaine.

But then this begs the question, why would one Restore a Database which already exists?

[Dwaine Maggart]

If you thought there was an issue with the current database, and you wanted to restore a backup.

...the Connect icon is now at the top of the Database area of the Project Manager page, next to the Backup and Restore icons.

Thank you so much, Dwaine! I had totally missed this.

connect.png (5.28 KiB) Viewed 2085 times

I still think it'd be nice to have a button that offers to [ Reconnect ] if the database already exists. But clicking the new "connect" icon worked great for me. Thank you, thank you, thank you!

~Luke

If you thought there was an issue with the current database, and you wanted to restore a backup.

OK.

Seems a weird thing to me, though. I think I'd rather get rid of the suspected faulty database first so I can keep the name.