| From: | "Jean-Yves F(dot) Barbier" <12ukwn(at)gmail(dot)com> |
|---|---|
| To: | Barry Laffoon <gotobarry(at)gmail(dot)com> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: Bit Varying vs New Column |
| Date: | 2011-07-04 19:41:25 |
| Message-ID: | 20110704214125.4f230e4c@anubis.defcon1 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Mon, 4 Jul 2011 12:26:48 -0700, Barry Laffoon <gotobarry(at)gmail(dot)com> wrote:
> I have a property on a web form that is multi-select so the property can
> have multiple values. Normally I'd create separate column or a separate row
> for each value. I am thinking of using the BIT VARYING() data type though
> and storing the selected values as a bit mask. So I have several related
> questions:
>
> 1. Any general comments on how this performs?
If you really need speed, consider using BOOLEAN - It is all a matter of
"speed" definition: if you have tons of concurrent requests use BOOLEAN.
--
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vincent Ficet | 2011-07-05 07:13:18 | Re: pg_advisory_locks in a multithreaded application context |
| Previous Message | Barry Laffoon | 2011-07-04 19:26:48 | Bit Varying vs New Column |