Thread: CTRL-Z in the SQL command editor.

CTRL-Z in the SQL command editor.

From
"Gaetan beaulieu"
Date:
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 :-(
 

Windows xp
French
Version 1.10.1 (Dec 3 2009, rev:8025:8026M)
 
Tank you!

Re: CTRL-Z in the SQL command editor.

From
Dave Page
Date:
On Wed, Apr 7, 2010 at 9:28 PM, Gaetan beaulieu <BeaG@sogi.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