From: | Zeugswetter Andreas SARZ <Andreas(dot)Zeugswetter(at)telecom(dot)at> |
---|---|
To: | "'pgsql-hackers(at)hub(dot)org'" <pgsql-hackers(at)hub(dot)org> |
Subject: | Permissions on copy |
Date: | 1998-02-20 11:02:52 |
Message-ID: | 219F68D65015D011A8E000006F8590C6010A51E6@sdexcsrv1.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Since the copy statement is behaving differently than the normal select
stuff,
I think we should eighter introduce a new permission (name it copy or dump)
or include the copy into the rewrite system.
I would vote for the first and implement a new command:
unload to <filename> [delimiter '|'] <select statement>; -- and
load from <filename> [delimiter '|'] <insert statement>;
that does behave like the select. (please forgive my Informix
background)
As to the topic with setuid triggers and others, I think setuid procedures
would be sufficient.
These are implemented in Informix with the following simple syntax:
create dba procedure ....
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 1998-02-20 11:20:21 | Re: [HACKERS] libpgtcl undefined symbol error with pgaccess-0.76 |
Previous Message | Jan Wieck | 1998-02-20 10:52:06 | Re: [HACKERS] Running pgindent |