Re: Refreshing Objects when their SQL-Script is copied into new SQL Window

From: Dave Page <dpage(at)postgresql(dot)org>
To: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: Refreshing Objects when their SQL-Script is copied into new SQL Window
Date: 2007-03-06 13:27:43
Message-ID: [email protected]
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Florian G. Pflug wrote:
> Hi
>
> When debugging plpgsql functions, I usually click on the
> function I want to edit, and then on the SQL Icon. This
> opens a new SQL Window, with the "CREATE FUNCTION.."
> Statement already filled on. If I now change the function,
> hit F5, close the window, and reopen it, I see the
> old version of the function. This leads to accidentally
> reverting your own changes, if you forget to hit "refresh"
> _before_ reopening the window.
>
> Would a patch that always refreshes an object before
> opening a SQL-Window that would contain it's create
> statement be accepted?

There is a mechanism in place to detect changes when opening the
properties dialog - perhaps that can be reused in this case?

Regards, Dave.

In response to

Browse pgadmin-hackers by date

  From Date Subject
Next Message svn 2007-03-06 15:39:35 SVN Commit by dpage: r5985 - trunk/pgadmin3/pgadmin/schema
Previous Message Dave Page 2007-03-06 13:25:07 Re: The "dependent" list shows _RULE if a view depends on something