Re: [QUESTIONS] Re: [HACKERS] text should be a blob field - Mailing list pgsql-hackers

From jwieck@debis.com (Jan Wieck)
Subject Re: [QUESTIONS] Re: [HACKERS] text should be a blob field
Date
Msg-id m0yEUlX-000BFRC@orion.SAPserv.Hamburg.dsh.de
Whole thread Raw
In response to Re: [QUESTIONS] Re: [HACKERS] text should be a blob field  (Peter T Mount <psqlhack@maidast.demon.co.uk>)
Responses Re: [QUESTIONS] Re: [HACKERS] text should be a blob field
List pgsql-hackers
Peter Mount wrote:
>
> On Wed, 4 Mar 1998, Jan Wieck wrote:
>
> >     I think triggers are more appropriate.
> >
>
> I'm begining to agree with you here.
>
> So far, I've got the trigger to work, so if a row of a table is deleted,
> or an oid referencing a BLOB is updated, then the old BLOB is deleted.
> This removes the orphaned BLOB problem.
>
> The only problem I have now, is:
>
>   How to get a trigger to be automatically created on a table when the
>   table is created. This would be required, so the end user doesn't have
>   to do this (normally from within an application).
>
> This would be required, esp. for expanding the text type (or memo, or
> whatever).

    So  you think of a new type that automatically causes trigger
    definition if used in CREATE/ALTER TABLE.

    Agree - would be a nice feature.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#======================================== jwieck@debis.com (Jan Wieck) #

pgsql-hackers by date:

Previous
From: jwieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] Re: PL/PgSQL discussion
Next
From: "Vadim B. Mikheev"
Date:
Subject: Re: [HACKERS] Re: [QUESTIONS] Does Storage Manager support >2GB tables?