Received: from indexapp00.indexc.net ([216.28.134.29]) by hub.org (8.9.3/8.9.3) with ESMTP id IAA23632; Wed, 31 May 2000 08:46:42 -0400 (EDT) (envelope-from twallingford@indexc.com) Received: by INDEXAPP00 with Internet Mail Service (5.5.2448.0) id ; Wed, 31 May 2000 08:45:56 -0400 Message-ID: <70866BD37E22D4119D8000600899F70D011CC3@INDEXAPP00> From: "Wallingford, Ted" To: "Wallingford, Ted" , "'pgsql-admin@postgresql.org'" Cc: pgsql-sql@postgresql.org Subject: create view security Date: Wed, 31 May 2000 08:45:55 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01BFCAFE.2A07F710" X-Archive-Number: 200005/55 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01BFCAFE.2A07F710 Content-Type: text/plain; charset="iso-8859-1" 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 > ------_=_NextPart_000_01BFCAFE.2A07F710 Content-Type: application/octet-stream; name="Wallingford, Ted.vcf" Content-Disposition: attachment; filename="Wallingford, Ted.vcf" BEGIN:VCARD VERSION:2.1 N:Wallingford;Ted FN:Wallingford, Ted EMAIL;PREF;INTERNET:twallingford@indexc.com REV:20000428T121410Z END:VCARD ------_=_NextPart_000_01BFCAFE.2A07F710--