Re: proposal: searching in array function - array_position

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: searching in array function - array_position
Date: 2015-01-26 22:29:19
Message-ID: 54C6BFBF.8080107@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1/26/15 4:17 PM, Pavel Stehule wrote:
> Any way to reduce the code duplication between the array and non-array versions? Maybe factor out the operator caching code?
>
>
> I though about it - but there is different checks, different result processing, different result type.
>
> I didn't find any readable and reduced form :(

Yeah, that's why I was thinking specifically of the operator caching code... isn't that identical? That would at least remove a dozen lines...
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2015-01-26 22:36:55 Re: New CF app deployment
Previous Message Stephen Frost 2015-01-26 22:23:28 Re: pgaudit - an auditing extension for PostgreSQL