From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | BeaG(at)sogi(dot)com |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: CTRL-Z in the SQL command editor. |
Date: | 2010-04-07 20:34:02 |
Message-ID: | i2v937d27e11004071334s18aae70k3df6743967be6376@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Wed, Apr 7, 2010 at 9:28 PM, Gaetan beaulieu <BeaG(at)sogi(dot)com> wrote:
> Hi!
> I found a little problem with the CTRL-Z in the SQL command editor.
>
> I have two files, each containing several SQL queries. sql_01.sql and
> sql_02.sql.
>
> I get the first file sql_01.sql from the menu, I run and everything is fine.
>
> I get the second file from the menu in the same edit window and I bring some
> changes.
>
> I did CTRL-Z to remove the last change and I see the SQL statements of the
> first file appear.
>
> So if I save the file, i loose the SQL queries in the file sql_02.sql.
>
> This could represent several hours of work :-(
The fact that the undo history includes file loads as an 'edit' rather
than a restart point is something I consider to be a feature. If you
ctrl-z too far, you can always ctrl-y to go back again.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Olivier Bouiron | 2010-04-09 07:29:24 | Re: pgpass |
Previous Message | Gaetan beaulieu | 2010-04-07 20:28:04 | CTRL-Z in the SQL command editor. |