X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 319AD56918 for ; Mon, 14 Mar 2005 15:29:32 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 57339-03 for ; Mon, 14 Mar 2005 15:29:29 +0000 (GMT) Received: from sranda.klamovka.kosire.czf (unknown [82.113.63.66]) by svr1.postgresql.org (Postfix) with ESMTP id 18B825686B for ; Mon, 14 Mar 2005 15:27:41 +0000 (GMT) Received: (qmail 27265 invoked from network); 14 Mar 2005 16:27:44 +0100 Received: from startnet.klamovka.kosire.czf (HELO ?192.168.11.101?) (10.15.6.17) by ns.klamovka.kosire.czf with AES256-SHA encrypted SMTP; 14 Mar 2005 16:27:44 +0100 Message-ID: <4235AD70.60407@startnet.cz> Date: Mon, 14 Mar 2005 16:27:44 +0100 From: =?windows-1252?Q?Miroslav_=8Aulc?= Organization: StartNet s.r.o. User-Agent: Mozilla Thunderbird 1.0 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: hf1122x@protecting.net Cc: pgsql-performance@postgresql.org Subject: Re: How to read query plan References: <42345D24.8070104@startnet.cz> <4234692E.3050802@arbash-meinel.com> <42347407.2000202@startnet.cz> <42347D5E.9000900@arbash-meinel.com> <42348F54.1000408@startnet.cz> <423493E5.6040203@arbash-meinel.com> <42355249.8090101@startnet.cz> <423556B8.4020500@startnet.cz> In-Reply-To: X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/mixed; boundary="------------080008030501040400020606" X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200503/262 X-Sequence-Number: 10967 This is a multi-part message in MIME format. --------------080008030501040400020606 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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 --------------080008030501040400020606 Content-Type: text/x-vcard; charset=utf-8; name="miroslav.sulc.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="miroslav.sulc.vcf" begin:vcard fn;quoted-printable:Miroslav =C5=A0ulc n;quoted-printable:=C5=A0ulc;Miroslav org:StartNet s.r.o. adr;quoted-printable;quoted-printable:;;Vrchlick=C3=A9ho 161/5;Praha 5;;150 00;=C4=8Cesk=C3=A1 republika email;internet:miroslav.sulc@startnet.cz title:CEO tel;work:+420 257 225 602 tel;cell:+420 603 711 413 x-mozilla-html:TRUE url:http://www.startnet.cz version:2.1 end:vcard --------------080008030501040400020606--