From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Bastiaan Olij <bastiaan(at)basenlily(dot)me> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: Some small UI improvements for backups/restores |
Date: | 2013-02-23 18:24:57 |
Message-ID: | 1361643897.15634.75.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hi,
On Thu, 2013-02-21 at 07:23 +1100, Bastiaan Olij wrote:
> [...]
> For those who are tinkering away at the product, here are two small
> suggestions that would improve my life loads:)
>
> When performing a backup or a restore could the title of the window
> (currently empty) show the database you are about to backup/restore into?
This was something I wanted to do since quite a long time. I pushed a
fix on this issue.
> Also could you add a check before running a restore that checks if there
> is already data in the database you are about to restore into?
I don't see how we could do such a thing reliably. And you may have data
but don't care because you really want to add data over old one.
> I've had a few times now that I selected the wrong database and
> restoring into a database that already has data in it gets really really
> messy:)
>
Yeah, I understand the use case, it happened to some of my customers
(though not with pgAdmin), and they were pretty angry with it.
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2013-02-23 18:28:36 | Re: query saved during crash |
Previous Message | Guillaume Lelarge | 2013-02-23 14:56:50 | Re: Problem with pgAdmin and Server Status encode |