Re: How to read query plan

From: Miroslav Šulc <miroslav(dot)sulc(at)startnet(dot)cz>
To: hf1122x(at)protecting(dot)net
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: How to read query plan
Date: 2005-03-14 15:27:44
Message-ID: 4235AD70.60407@startnet.cz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

Harald Fuchs wrote:

>>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.
>
>
I know that. The time will have to come.

>(*) MySQL recognizes BOOL as a column type and silently uses
>TINYINT(1) instead.
>
>
I've checked that and you are right, but the BOOL is in MySQL from
version 4.1.0 though we could use tinyint instead of enum - our bad choice.

Miroslav

Attachment Content-Type Size
miroslav.sulc.vcf text/x-vcard 387 bytes

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2005-03-14 15:49:04 Re: [BUGS] We are not following the spec for HAVING without GROUP
Previous Message Miroslav Šulc 2005-03-14 15:21:37 Re: [PERFORM] How to read query plan

Browse pgsql-performance by date

  From Date Subject
Next Message John Arbash Meinel 2005-03-14 15:54:29 Re: [PERFORM] How to read query plan
Previous Message Miroslav Šulc 2005-03-14 15:21:37 Re: [PERFORM] How to read query plan