From: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | James Robinson <jlrobins(at)socialserve(dot)com>, Hackers Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Postgres / plpgsql equivalent to python's getattr() ? |
Date: | 2011-08-04 14:00:25 |
Message-ID: | 1312466425.4917.21.camel@hvost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2011-08-03 at 18:48 -0400, Tom Lane wrote:
> James Robinson <jlrobins(at)socialserve(dot)com> writes:
> > Python's getattr() allows for dynamic lookup of attributes on an
> > object, as in:
>
> > inst = MyClass(x=12, y=24)
> > v = getattr(inst, 'x')
> > assert v == 12
>
> > Oftentimes in writing data validating trigger functions, it'd be real
> > handy to be able to do a similar thing in plpgsql
>
> > Is there something in the internals which inherently prevent this?
>
> plpgsql is strongly typed (much more so than python, anyway).
For example the plpgsql type RECORD is about as strongly typed as (some)
python classes , that is once assigned the record itself is typed, but
the same variable can point to different record types
--
-------
Hannu Krosing
PostgreSQL Infinite Scalability and Performance Consultant
PG Admin Book: http://www.2ndQuadrant.com/books/
From | Date | Subject | |
---|---|---|---|
Next Message | James Robinson | 2011-08-04 14:10:02 | Re: Postgres / plpgsql equivalent to python's getattr() ? |
Previous Message | Hannu Krosing | 2011-08-04 13:53:40 | Re: plperl crash with Debian 6 (64 bit), pl/perlu, libwww and https |