Re: Refreshing Objects when their SQL-Script is copied into new SQL Window - Mailing list pgadmin-hackers

From Dave Page
Subject Re: Refreshing Objects when their SQL-Script is copied into new SQL Window
Date
Msg-id 45ED6C4F.6040106@postgresql.org
Whole thread Raw
In response to Refreshing Objects when their SQL-Script is copied into new SQL Window  ("Florian G. Pflug" <fgp@phlo.org>)
List 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.

pgadmin-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: The "dependent" list shows _RULE if a view depends on something
Next
From: svn@pgadmin.org
Date:
Subject: SVN Commit by dpage: r5985 - trunk/pgadmin3/pgadmin/schema