Re: prepared statements

From: "David Johnston" <polobo(at)yahoo(dot)com>
To: "'Pavel Stehule'" <pavel(dot)stehule(at)gmail(dot)com>, "'Vad N'" <vadimid(at)gmail(dot)com>
Cc: <pgsql-sql(at)postgresql(dot)org>
Subject: Re: prepared statements
Date: 2011-12-08 14:42:58
Message-ID: 050101ccb5b7$aeb96510$0c2c2f30$@yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

-----Original Message-----
From: pgsql-sql-owner(at)postgresql(dot)org [mailto:pgsql-sql-owner(at)postgresql(dot)org] On Behalf Of Pavel Stehule
Sent: Thursday, December 08, 2011 2:40 AM
To: Vad N
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: [SQL] prepared statements

Hello

2011/12/8 Vad N <vadimid(at)gmail(dot)com>:
>
> Hi.
>
> How can i pass a set of values to prepared statement?
>
> example
> I have a prepared query:
> select * from users in ( $1 )
>
> i would like to pass: 1,2,3,4 and get:
>
> select * from users in ( 1,2,3,4 )
>
> Any ideas?

use a array parameter, please

regards

Pavel Stehule

------------------------------------------------------------------

Or, in lieu of readily passing arrays from your client API you can always pass a string and modify the query to parse the string into an array.

... users = ANY ( regexp_split_to_array( $1, ',' )::integer[] )

David J.

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Craig Ringer 2011-12-09 01:13:11 Re: partitions versus databases
Previous Message chester c young 2011-12-08 14:26:09 partitions versus databases