From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
Cc: | "PostgreSQL Development" <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: CREATE CAST code review |
Date: | 2002-07-23 07:39:21 |
Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA4961E27@m0114.s-mxs.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > That doesn't quite work, because then no ordinary user can define a cast
> > from some built-in type to his own type. What I'm thinking about is to
> > implement the USAGE privilege on types, and then you need to have that to
> > be allowed to create casts.
>
> Still seems too weak.
Yes.
> What about requiring ownership of at least one
> of the types?
I was thinking that too, but, would it be possible to circumvent such
a restriction with a "type in the middle" attack ?
Create your own type and then
1. (auto)cast type1 to own type
2. (auto)cast own type to type2 ?
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Treat | 2002-07-23 14:03:25 | Re: Stats Collector |
Previous Message | Joe Conway | 2002-07-23 03:59:24 | Re: Access Two Databases |