"Florian G. Pflug" <[email protected]> writes:
> I'd like to replace this function-generating function by a generic
> trigger function that works for all tables. Due to the lack of any way
> to inspect the *structure* of a record type, however, I'd have to use a
> C language function for that, which induces quite some maintenance
> headaches (especially if deployed on windows).
Trying to do this in plpgsql is doomed to failure and heartache, because
it's fundamentally a strongly typed language. The proposed functions
won't fix that and hence will be unusable in practice. I'd suggest
either using C, or using one of the less-strongly-typed PLs.
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
