| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Richard Broersma Jr <rabroersma(at)yahoo(dot)com> |
| Cc: | Jon Collette <jon(at)etelos(dot)com>, SQL Postgresql List <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: Boolean without default declared |
| Date: | 2007-08-15 21:48:19 |
| Message-ID: | 7678.1187214499@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Richard Broersma Jr <rabroersma(at)yahoo(dot)com> writes:
> --- Jon Collette <jon(at)etelos(dot)com> wrote:
>> Thanks that was it exactly. I did notice another strange thing. When
>> using IS NULL in an plpgsql IF statement you have to use ISNULL. Same
>> with NOT NULL. Does this mean that ISNULL is more proper than IS NULL?
IS NULL is in the SQL standard, the other is not; and I dunno what you did
wrong but you certainly don't "have to" use ISNULL in plpgsql.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Javier Fonseca V. | 2007-08-16 00:05:51 | Re: Trigger Procedure Error: NEW used in query that is not in a rule |
| Previous Message | Michael Glaesemann | 2007-08-15 21:04:37 | Re: Problem with phone list. |