| From: | Harald Fuchs <use_reply_to(at)protecting(dot)net> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: How to read query plan |
| Date: | 2005-03-14 14:05:52 |
| Message-ID: | puekei9vb3.fsf@srv.protecting.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
In article <423556B8(dot)4020500(at)startnet(dot)cz>,
=?ISO-8859-15?Q?Miroslav_=A6ulc?= <miroslav(dot)sulc(at)startnet(dot)cz> writes:
>> Instead of a varchar(1) containing 'y' or 'n' you could use a
>> BOOL or an integer.
> Sure I could. The problem is our project still supports both MySQL and
> PostgreSQL. We used enum('Y','N') in MySQL so there would be a lot of
> changes in the code if we would change to the BOOL data type.
Since BOOL is exactly what you want to express and since MySQL also
supports BOOL (*), you should make that change anyway.
(*) MySQL recognizes BOOL as a column type and silently uses
TINYINT(1) instead.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-03-14 15:03:01 | Re: [PERFORM] How to read query plan |
| Previous Message | Harald Fuchs | 2005-03-14 13:12:39 | Re: invalidating cached plans |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2005-03-14 14:50:21 | Re: adding 'limit' leads to very slow query |
| Previous Message | Camille Chafer | 2005-03-14 11:54:58 | Hardware impact on performances |