| From: | "Rod Taylor" <rbt(at)zort(dot)ca> |
|---|---|
| To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Joe Conway" <mail(at)joeconway(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Schema (namespace) privilege details |
| Date: | 2002-04-19 02:22:19 |
| Message-ID: | 042901c1e749$08927790$8001a8c0@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> That is, of course, a BSD-ism that would confuse a lot of the SysV
people...
> :)
Yup.. But it's been around quite a while and I don't know of any
horrible problems with it -- that said I've not actually tried it on
OpenBSD (different mindset) but would be surprised if it wasn't the
same.
Sure, it may not be the smartest thing to allow user Y to create a
table in my schema BUT if I decide to reverse that decision (for
whatever reason) I want to be able to drop the junk user Y littered
around my schema along with the user even if I'm not allowed to look
at it, use it or otherwise fiddle around with it.
But if I'm the only one who feels this way, so be it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2002-04-19 02:24:41 | Re: Schema (namespace) privilege details |
| Previous Message | Steffen Nielsen | 2002-04-19 02:15:49 | Getting Constrint information..?? |