Re: Generic timestamp function for updates where field

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: novnov <novnovice(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Generic timestamp function for updates where field
Date: 2006-12-31 16:54:55
Message-ID: 20061231165455.GC6777@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Dec 31, 2006 at 08:48:07AM -0800, novnov wrote:
> Why would not be possible in plpgsql? It has loop etc, the only part I'm not
> sure it can do it use the variable as field name.

The "dynamic" in dynamic language usually refers to dynamic typing.
pl/pgsql is a strictly typed language which means one can look at the
code and determine what type each variable will be.

Languages like perl and python are dynamic because what type a variable
is does not matter until runtime and the type can change every time you
run it.

The problem with using a variable as a field name is that you can no
longer tell what type the result will be. It could be any type
supported by postgres. pl/pgsql can't handle that, perl and python
can...

Hope this helps,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Richard Broersma Jr 2006-12-31 17:00:50 Re: slow speeds after 2 million rows inserted
Previous Message novnov 2006-12-31 16:52:23 Re: Generic timestamp function for updates where field