Search Postgresql Archives

Re: plpgsql and control structures

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jan 30, 2009 at 02:08:19PM -0800, Nick Boutelier wrote:
> I noticed that if I use...
> 
> IF (TG_OP = 'DELETE' AND OLD.myColumn) THEN
>   -- Do something
> END IF;
> 
> when an insert happens, I get an error that 'OLD' has not been
> assigned. I would of thought that the control structure would just
> ignored the rest of the 'if' statement if the first part (TG_OP) was
> false.

SQL is not C, AND and OR in if statements do not short-circuit.

> Does this mean I have to branch out my control structures if I want
> better speed? If the first part of the 'if' is rarely true, then I
> might as well put the second control within the first.

Nothing to do with speed, the entire expression needs to be parsable at
the point it is executed. So in your above example you need to nest two
if statements.

Have a nice day,
-- 
Martijn van Oosterhout   <kleptog@xxxxxxxxx>   http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while 
> boarding. Thank you for flying nlogn airlines.

Attachment: signature.asc
Description: Digital signature


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux