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 C1E6756662 for ; Mon, 14 Mar 2005 15:10:43 +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 49970-06 for ; Mon, 14 Mar 2005 15:10:33 +0000 (GMT) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by svr1.postgresql.org (Postfix) with ESMTP id 357A7563D9 for ; Mon, 14 Mar 2005 15:10:32 +0000 (GMT) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1DAr3g-0003QB-38 for pgsql-performance@postgresql.org; Mon, 14 Mar 2005 16:00:41 +0100 Received: from srv.protecting.net ([212.126.218.242]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 14 Mar 2005 16:00:40 +0100 Received: from hf1122x by srv.protecting.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 14 Mar 2005 16:00:40 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: pgsql-performance@postgresql.org From: Harald Fuchs Subject: Re: How to read query plan Date: 14 Mar 2005 15:05:52 +0100 Organization: Linux Private Site Lines: 15 Message-ID: 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> Reply-To: hf1122x@protecting.net Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: srv.protecting.net User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 X-Gmane-MailScanner: Found to be clean X-Gmane-MailScanner: Found to be clean X-MailScanner-From: gcdpp-pgsql-performance@m.gmane.org X-MailScanner-To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200503/260 X-Sequence-Number: 10965 In article <423556B8.4020500@startnet.cz>, =?ISO-8859-15?Q?Miroslav_=A6ulc?= 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.