Re: [HACKERS] Permissions on copy - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: [HACKERS] Permissions on copy
Date
Msg-id Pine.NEB.3.95.980220115608.11437J-100000@hub.org
Whole thread Raw
In response to Re: [HACKERS] Permissions on copy  (Bruce Momjian <maillist@candle.pha.pa.us>)
Responses Re: [HACKERS] Permissions on copy  (Bruce Momjian <maillist@candle.pha.pa.us>)
List 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...



pgsql-hackers by date:

Previous
From: "Thomas G. Lockhart"
Date:
Subject: Re: [HACKERS] Recursive queries?
Next
From: "Thomas G. Lockhart"
Date:
Subject: Re: [HACKERS] Subselects and NOTs