On 12/13/05, Owen Jacobson <oj= acobson@osl.com> wrote:

Daniel Hertz wrote:

> Given a set of checkbox values that are sub= mitted through an
> html form,
> how do you loop through the su= bmitted values to update more
> than one row
> in a table?
>
> Imagine a table called 'message_table':
>
> mid | = message | status
> ----+---------+-------
>   1 = |  Text1   |  H
>   2&n= bsp; |  Text2   |  H
>  = 3  |  Text3   |  H
> &n= bsp; 4  |  Text4   |  H
>
> A web page presents the user with all messages flagged wit= h 'H'. User
> checks messages 1,3 and 4 and submits form.
> (i.= e. approved=3D1&approved=3D3&approved=3D4)
>
> After pe= rforming postgreSQL update, rows 1, 3 and 4 would be
> updated to:
>
> mid | message | status
> ----+--= -------+-------
>   1  |  Text1 &n= bsp; |  A
>   2  |  Text2&nbs= p; |  H
>   3  |  Text3=    |  A
>   4  |  T= ext4   |  A

BEGIN;
UPDATE message_table SET status =3D 'A' WHERE mid =3D 1;
UPDATE message_= table SET status =3D 'A' WHERE mid =3D 3;
UPDATE message_table SET statu= s =3D 'A' WHERE mid =3D 4;
COMMIT;

would do that.  Have your application generate an appropriate UPDATE line for each "approved" entry in the form data, wrap it i= n a transaction, and away you go.

> I have never written a plpgsql fu= nction, but tried:
>
> CREATE OR REPLACE FUNCTION update_messag= es(approved integer) RETURNS
> integer AS
> $body$
> DECL= ARE
>  new_status varchar;
>  new_sample recor= d;
>
> BEGIN
>  new_status :=3D 'A';
>>  FOR new_sample IN SELECT * FROM message_table WHERE
>= ; status=3D'H' ORDER BY
> mid LOOP

1.  No need for ORDER BY here, we're not doing anything user-visible or order-dependent with the data, so it's a waste of CPU time.
2. &nbs= p;You're not using new_sample for anything, just retrieving it.

>=    UPDATE message_table SET status =3D new_status
> &n= bsp; WHERE mid =3D approved;

Consider that you can only pass a single value to an INTEGER parameter ("approved"); this will repeatedly update a single entry where mi= d =3D approved.  You could simplify the function as written to

C= REATE OR REPLACE FUNCTION update_messages (INTEGER) RETURNS VOID AS $$
&= nbsp; UPDATE message_table SET status =3D 'A' WHERE mid =3D $1;
$$ = LANGUAGE SQL;

>  END LOOP;
>
>  RETURN 1;
> END;=
> $body$
> LANGUAGE 'plpgsql' VOLATILE CALLED ON NULL INPUT SE= CURITY INVOKER;
>
> I call the function with:
> SELECT up= date_messages(<xsp-request:get-parameter name=3D"approved"/>= ;);
>
> I'm using apache cocoon, which is why you see the variable=
> placeholder:
> <xsp-request:get-parameter name=3D"ap= proved"/>);

I'm not familiar with Cocoon, but I'd expect that to return only the first of the "approved" values from the HTTP request.  If you= add logging to the stored function (RAISE NOTICE 'approved: %', approved; near the start of the function, for instance) and tell PostgreSQL to store the logs, you can see what values your function is actually being called with.

What you really want to do is begin a transaction, loop over all the values of approved present in the form data and call (the rewritten version of) update_messages for each one, then commit the transaction.

-Owen

---------------------------(end of bro= adcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster=