Re: Functions, savepoints, autocommit = I am confused !

From: Tim Smith <randomdev4+postgres(at)gmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Functions, savepoints, autocommit = I am confused !
Date: 2015-06-26 16:54:45
Message-ID: CA+HuS5HRxDp3Cc+GThSdxysccuA-PvyLcgFhXBMeY9gqxgn8gg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> Well that was my problem, I did not know what was intended.

apt-get install mind-reading ;-)

> 1) Look before you leap
>

I'm confused by this option ?

My script reads as follows :
perform app_security.cleanSessionTable(p_forcedTimeout,p_sessionTimeout);
select * into strict v_row from app_security.app_val_session_vw where
session_id=p_session_id and session_ip=p_client_ip and
session_user_agent=p_user_agent;
update app_security.app_sessions set session_lastactive=v_now where
session_id=p_session_id;

Its the "select * into strict" that's causing me grief, not the
"update", isn't it ?!?

>
> 2) Act and then ask for forgiveness.
>
> You can have more then one BEGIN/END block in plpgsql. So you could put the
> update in its own block and catch the exception there.

I'll give that a go. I thought it might be an option, but it was not
too clear from the docs whether the sub-blocks were treated as
seperate transactions when used within a function.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tim Smith 2015-06-26 17:02:42 Re: Functions, savepoints, autocommit = I am confused !
Previous Message Adrian Klaver 2015-06-26 16:23:33 Re: Functions, savepoints, autocommit = I am confused !