Re: stored function, multiple queries, best practices

From: Ash Grove <ash_grv7(at)yahoo(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: stored function, multiple queries, best practices
Date: 2006-04-14 14:37:20
Message-ID: 20060414143720.5342.qmail@web52512.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Jeff Hubbach 2006-04-14 14:53:07 Re: Possible regression: setNull() usage changed from 7.4 to
Previous Message Oliver Jowett 2006-04-14 14:18:58 Re: stored function, multiple queries, best practices