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 20060418185351.89200.qmail@web52501.mail.yahoo.com
Whole thread Raw
In response to Re: stored function, multiple queries, best practices  (Oliver Jowett <oliver@opencloud.com>)
List pgsql-jdbc

--- Oliver Jowett <oliver@opencloud.com> wrote:

> Ash Grove wrote:
> >
> >>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')"?
>
> No, I'm suggesting:
>
>    call myfunction('data value 1', 42, 1.234, 'data
> value 4')
>
> I am assuming you know the combinations of updates
> you will need to run
> ahead of time. If you want to run arbitary queries
> then you are probably
> stuck with doing some parsing in the function .. but
> that is pretty nasty.
>
> -O
>

I know the combination of queries, but whether a
parameter has a value is unknown. Also unknow is
whether all relevant tables will get updated. If I
simply send all parameters in a defined order, the
parameter list will be kinda long and many values will
be nulls.

I can only call one function (from the application)
per transaction, right?

I don't mind doing the parsing, I was just wondering
if I was considering all options.

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

pgsql-jdbc by date:

Previous
From: Mark Lewis
Date:
Subject: Re: [SQL] Thoughts on a Isolation/Security problem.
Next
From: "Guy Rouillier"
Date:
Subject: Re: stored function, multiple queries, best practices