On Mon, Apr 7, 2008 at 3:59 AM, Gregory Stark [EMAIL PROTECTED] wrote:
I wonder if there's much of a use case for any statements aside from CREATE
statements. If we restrict it to CREATE statements we could hack things to
create pg_depend entries automatically. In which case we wouldn't need
On Mon, Apr 7, 2008 at 11:46 AM, Tom Dunstan [EMAIL PROTECTED] wrote:
On Mon, Apr 7, 2008 at 3:59 AM, Gregory Stark [EMAIL PROTECTED] wrote:
I wonder if there's much of a use case for any statements aside from
CREATE
statements. If we restrict it to CREATE statements we could hack
Sorry to keep replying to myself, but part of the point of doing a
patch was to force myself (and whoever else is interested to examine
stuff that comes up...
On Mon, Apr 7, 2008 at 11:46 AM, Tom Dunstan [EMAIL PROTECTED] wrote:
None of that suggests that an uninstaller script would be needed
Tom Dunstan [EMAIL PROTECTED] writes:
OK, I found an example that does NOT fit the just drop all
dependencies scenario, but that I would still like to support. I just
had a look at the postgis pl/java support, and its install does stuff
like SELECT
On Mon, Apr 7, 2008 at 7:55 PM, Tom Lane [EMAIL PROTECTED] wrote:
Tom Dunstan [EMAIL PROTECTED] writes:
OK, I found an example that does NOT fit the just drop all
dependencies scenario, but that I would still like to support. I just
had a look at the postgis pl/java support, and its
Tom Dunstan [EMAIL PROTECTED] writes:
- I'd like to add pg_depend entries for stuff installed by the module
on the pd_module entry, so that you can't drop stuff required by the
module without uninstalling the module itself. There would have to be
either a function or more syntax to allow a
