From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Zeugswetter Andreas SARZ <Andreas(dot)Zeugswetter(at)telecom(dot)at>, pgsql-hackers(at)hub(dot)org |
Subject: | Re: [HACKERS] Permissions on copy |
Date: | 1998-02-20 16:56:47 |
Message-ID: | Pine.NEB.3.95.980220115608.11437J-100000@hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 20 Feb 1998, Bruce Momjian wrote:
> >
> > 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)
>
> Yes, I agree the Informix way of having load/unload, and having a SELECT
> capability so you can dump any data/join you want, not just a single
> table. Do I have votes to put this on the TODO list?
I'm not quite sure what we are voting on here...is it to implement
permissions on a copy, like we do on 'select/delete/insert/etc'?
If so, count me in...
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-02-20 17:00:15 | Re: [HACKERS] Who is everyone? |
Previous Message | Bruce Momjian | 1998-02-20 16:55:23 | Re: [HACKERS] Subselects and NOTs |