Re: stored function, multiple queries, best practices - Mailing list pgsql-jdbc

From Ash Grove
Subject Re: stored function, multiple queries, best practices
Date
Msg-id 20060414143720.5342.qmail@web52512.mail.yahoo.com
Whole thread Raw
In response to Re: stored function, multiple queries, best practices  (Oliver Jowett <oliver@opencloud.com>)
Responses Re: stored function, multiple queries, best practices
List pgsql-jdbc

>Why assemble a string and parse it? Why not just use
>multiple parameters
>directly?
>-O


So, Oliver,  you're suggesting something like "call
myfunction('query1','query2','query3')"?

> I currently do this by building a delimited string
> in
> the application containing all data to be inserted
> and
> then sending it, via callablestatement, to a
> stored
> function. The function parses the string, does the
> inserts and returns the primary key via a
> registered
> out parameter.
>
Why assemble a string and parse it? Why not just use
multiple parameters
directly?

 -O


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

pgsql-jdbc by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: stored function, multiple queries, best practices
Next
From: Jeff Hubbach
Date:
Subject: Re: Possible regression: setNull() usage changed from 7.4 to