| From: | <operationsengineer1(at)yahoo(dot)com> |
|---|---|
| To: | PostgreSQL Novice <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Boolean |
| Date: | 2005-02-25 20:02:17 |
| Message-ID: | 20050225200217.97456.qmail@web52402.mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-novice |
hi all,
i have a question about booleans. i heard that a
boolean takes more processing power than setting an
integer as 1 or 0 and coding around those values. is
this really an issue anyone will notice?
also, i understand that db portablility is somewhat
compromised when one uses pg's boolean data type.
are these really issues or am i over analyzing here?
tia...
__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-02-25 20:12:47 | Re: Boolean |
| Previous Message | Tom Lane | 2005-02-25 19:40:25 | Re: CAN-2005-0247 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-02-25 20:12:47 | Re: Boolean |
| Previous Message | Ross Gohlke | 2005-02-25 01:03:50 | Using upper() / decode() together |