* Vincent Veyron (vv(dot)lists(at)wanadoo(dot)fr) wrote:
> Would you mind giving an example of where a boolean field would be a win
> over an integer one?
Where you only ever want 2 (or perhaps 2+NULL) values allowed for the
column. It's about domain, consistency, etc, primairly. That said,
don't we implement boolean fields using a bitmap similar to NULLs? In
which case, it would likely be smaller on disk and more performant as
> I'm asking this because I frequently wonder what is best for my use; I
> normally query postgres via Perl modules, which don't care about boolean
> (the driver converts t/f to 0/1), but I like to tune my fields properly.
Yes, which is pretty horrible of it, imo.
In response to
pgsql-general by date
|Next:||From: sfrost||Date: 2011-06-26 16:12:11|
|Subject: Re: An amusing MySQL weakness--not!|
|Previous:||From: Tom Lane||Date: 2011-06-26 15:11:44|
|Subject: Re: Reusing cached prepared statement slow after 5 executions |