rüngliche Nachricht-
> Von: Damon Cokenias [mailto:[EMAIL PROTECTED]]
> Gesendet: Freitag, 19. April 2002 11:04
> An: pgsql-hackers
> Betreff: [HACKERS] Large object security
>
>
> Hi all,
>
> I see there's a TODO item for large object security, it's a feature
At 12:11 PM +0200 4/19/02, Mario Weilguni wrote:
>would'nt it be much better to expand pg_largeobject to have another column "src_oid"
>(or similar), containing the OID of the referencing table from pg_class, and when
>accessing large objects take the privilieges from the referencing class?
It'
"Mario Weilguni" <[EMAIL PROTECTED]> writes:
> would'nt it be much better to expand pg_largeobject to have another
> column "src_oid" (or similar), containing the OID of the referencing
> table from pg_class,
What referencing table? The existing LO implementation has no idea
where you are keepin
Damon Cokenias [mailto:[EMAIL PROTECTED]]
Gesendet: Freitag, 19. April 2002 11:04
An: pgsql-hackers
Betreff: [HACKERS] Large object security
Hi all,
I see there's a TODO item for large object security, it's a feature I'd really like to
see. I'm willing to put in the tim
Hi all,
I see there's a TODO item for large object security, it's a feature I'd really like to
see. I'm willing to put in the time to write a patch, but know far to little about
postgres internals and history to just dive in. Has there been any discussion on this
list about what this feature
