Can you do the whole thing inside a transaction context (both the
version check and the updates)? The exception should cause the
transaction to bail out, and the updates won't proceed.
UPDATE agenda_version set version = '188.8.131.52' where id = 1;
I tried it with your script and it seemed to work for me.
Hope this helps...
> Tom Lane wrote:
>> Arnau <arnaulist(at)andromeiberica(dot)com> writes:
>>> I don't want, if it's possible, to create a function.
>> Unlike Oracle, PG makes a strong distinction between SQL and
>> programmable languages (including plpgsql). You can't write
>> plpgsql code without putting it into a function.
>> regards, tom lane
> I've tried Daniel's suggestion but the Raise doesn't terminate the
> script execution, so if doesn't do what I need. Notice the Update 1
> arebassa(at)beowulf:~$ psql -d dermagier -f upgrade_agenda.sql
> CREATE FUNCTION
> psql:upgrade_agenda.sql:16: ERROR: This script needs Agenda version
> 184.108.40.206, detected version 220.127.116.11
> UPDATE 1
In response to
pgsql-sql by date
|Next:||From: roopa perumalraja||Date: 2006-12-29 01:05:04|
|Subject: Help in altering the column lenght|
|Previous:||From: Arnau||Date: 2006-12-28 18:20:55|
|Subject: Re: help with version checking|