The problem with this is that the existing functionality of LOs allows
you to share a single LO across multiple tables. There may not be a
single source, but multiple. Since LOs just use an OID as a FK to the
LO, you can store that OID in multiple different tables.
--Barry
Mario Weilguni wr
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
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?
-Ursprüngliche Nachricht-
Von: Damon Cokenias [
