Bitter experience... I am going to cc Dave here, because I could swear
we went through many conniptions trying to make this work.
And yet I just did this:
create view mytables as select relname from pg_class where relam = 0
and relname not like 'pg_%';
And it seems to work fine.
Oh, now I
Paul Ramsey [EMAIL PROTECTED] writes:
Oh, now I remember. The deal was not views, it was triggers.
Oh, okay. You're right, we don't do triggers on system tables. But
couldn't you combine a view on the system tables with storage of
additional data outside?
regards, tom
On Mon, 19 Jan 2004, Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
Just had a client point this out to me, and am wondering if its supposed
to happen:
420_test= select
dropgeometrycolumn('420_test','lroadline61','roads61_geom');
ERROR: permission denied for relation
Marc G. Fournier [EMAIL PROTECTED] writes:
On Mon, 19 Jan 2004, Tom Lane wrote:
in particular, what SQL command is it trying to execute when it chokes?
The function is executing:
EXECUTE ''update pg_attribute set attnotnull = false from pg_class where
On Tue, 20 Jan 2004, Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
On Mon, 19 Jan 2004, Tom Lane wrote:
in particular, what SQL command is it trying to execute when it chokes?
The function is executing:
EXECUTE ''update pg_attribute set attnotnull = false from pg_class
Marc G. Fournier [EMAIL PROTECTED] writes:
So, if we replace that with:
ALTER TABLE table_name ALTER column_name DROP NOT NULL; ?
should be good to go? still not as clean as doing the straight DROP
COLUMN, but its a fast fix ...
Yeah, that's what I'd do until the PostGIS guys can rethink
