From: Wallingford, Ted <twallingford@indexc.com>
To: Wallingford, Ted <twallingford@indexc.com>
To: 'pgsql-admin@postgresql.org' <pgsql-admin@postgresql.org>
Cc: pgsql-sql@postgresql.org
Subject: create view security
Date: Wed, 31 May 2000 08:45:55 -0400
Message-ID: <70866BD37E22D4119D8000600899F70D011CC3@INDEXAPP00> (raw)
Hi All,
I am trying to enable my web site to create views in a database owned by a
user called ddirpts. Now, the web server runs as nobody, and nobody has a
user and database set up in Postgres.. But the problem is, whenever I have a
cgi program issue a create view query on the ddirpts database, the backend
reports Parse error at or near "". I can however issue create view commands
as ddirpts.
I was thinking this might be a security restriction, wherein no user can
create views/tables in another user's database without some kind of special
permission--problem is, how do I create the permission?
I am using 6.3 in this case.
_________________________________________________
Ted Wallingford
Manager of Information Technology
Independence Excavating, Inc.
Precision Environmental Co.
Independence Communications, Inc.
www.indexc.com
> -----Original Message-----
> From: Thomas Lockhart [mailto:lockhart@alumni.caltech.edu]
> Sent: Tuesday, May 30, 2000 10:04 PM
> To: Tom Lane
> Cc: Peter Eisentraut; Joseph Shraibman; pgsql-sql@postgresql.org;
> pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Re: [SQL] aliases break my query
>
>
> > At one time Bruce had made some patches to emit informative notice
> > messages about implicit FROM entries, but that got turned off again
> > for reasons that I forget...
>
> It was triggered with common cases from the "outer join"
> syntax. It took
> a while to track down since it was introduced while I was
> working on the
> syntax feature :(
>
> If it *really* needs to be put back in, then we should do so
> with a flag
> so we can disable the warning at compile time, run time, and/or in the
> outer join parser area. But imho sprinkling the parser with
> warnings for
> allowed syntax is heading the wrong direction. If it is
> legal, allow it.
> If it is illegal, disallow it. If it is confusing for some, but works
> fine for others, it shouldn't become "sort of legal" with a warning.
>
> - Thomas
>
Attachments:
Wallingford, Ted.vcf (application/octet-stream, 136B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: twallingford@indexc.com, pgsql-admin@postgresql.org
Subject: Re: create view security
In-Reply-To: <70866BD37E22D4119D8000600899F70D011CC3@INDEXAPP00>
References: <70866BD37E22D4119D8000600899F70D011CC3@INDEXAPP00>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox