Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: IMMUTABLE?
- From: David Wheeler <david(at)kineticode(dot)com>
- To: Christopher Kings-Lynne <chris(dot)kings-lynne(at)calorieking(dot)com>
- Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance <pgsql-performance(at)postgresql(dot)org>
- Subject: Re: IMMUTABLE?
- Date: Tue, 16 May 2006 19:08:51 -0700
On May 16, 2006, at 18:29, Christopher Kings-Lynne wrote:
Yes, but there are definitely programming cases where memoization/ caching definitely helps. And it's easy to tell for a given function whether or not it really helps by simply trying it with CACHED and without.Would this be a simple thing to implement?It's called a "table" :)
http://www.justatheory.com/computers/databases/postgresql/ higher_order_plpgsql.html
Yes, I know. :-P But it'd be easier to have a CACHED keyword, of course. Best, David
- Follow-Ups:
- Re: IMMUTABLE?
- From: Jim C. Nasby
- Re: IMMUTABLE?
- References:
- IMMUTABLE?
- From: David Wheeler
- Re: IMMUTABLE?
- From: Tom Lane
- Re: IMMUTABLE?
- From: David Wheeler
- Re: IMMUTABLE?
- From: Tom Lane
- Re: IMMUTABLE?
- From: David Wheeler
- Re: IMMUTABLE?
- From: Christopher Kings-Lynne
- IMMUTABLE?
- Prev by Date: Re: Speed Up Offset and Limit Clause
- Next by Date: Re: Speed Up Offset and Limit Clause
- Previous by thread: Re: IMMUTABLE?
- Next by thread: Re: IMMUTABLE?
- Indexes: