| From: | "Joel Burton" <joel(at)joelburton(dot)com> |
|---|---|
| To: | "Stephan Szabo" <sszabo(at)megazone23(dot)bigpanda(dot)com>, "Alan Wayne" <alanjwayne(at)yahoo(dot)com> |
| Cc: | "Jean-Michel POURE" <jm(dot)poure(at)freesurf(dot)fr>, "pgsql-general" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Help with "empty()" |
| Date: | 2002-05-24 15:18:14 |
| Message-ID: | JGEPJNMCKODMDHGOBKDNOEHACPAA.joel@joelburton.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> -----Original Message-----
> From: pgsql-general-owner(at)postgresql(dot)org
> [mailto:pgsql-general-owner(at)postgresql(dot)org]On Behalf Of Stephan Szabo
> Sent: Friday, May 24, 2002 12:15 AM
> To: Alan Wayne
> Cc: Jean-Michel POURE; pgsql-general
> Subject: Re: [GENERAL] Help with "empty()"
>
> I'd have suggested writing empty functions for various
> types, empty(boolean), empty(int4), empty(float8),
> empty(text) and using those. You could probably even
> just do them as sql functions.
Yep. Though, since they're compiled, plpgsql functions are faster than SQL
functions. Don't forget to mark them as isCachable, too.
- J.
Joel BURTON | joel(at)joelburton(dot)com | joelburton.com | aim: wjoelburton
Knowledge Management & Technology Consultant
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Moritz Sinn | 2002-05-24 15:21:12 | Re: user defined variables |
| Previous Message | Braud Agnes | 2002-05-24 14:31:07 | Using the EXPLAIN results |