Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by hub.org (8.10.1/8.10.1) with ESMTP id e9CJWWr09607 for ; Thu, 12 Oct 2000 15:32:32 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.0/8.11.0) with ESMTP id e9CJWQB27093; Thu, 12 Oct 2000 15:32:30 -0400 (EDT) To: "Franz J Fortuny" cc: "sqllist" Subject: Re: Standard syntax? In-reply-to: <00fb01c03474$193888c0$3167a8c0@chapur> References: <00fb01c03474$193888c0$3167a8c0@chapur> Comments: In-reply-to "Franz J Fortuny" message dated "Thu, 12 Oct 2000 12:44:40 -0500" Date: Thu, 12 Oct 2000 15:32:26 -0400 Message-ID: <27090.971379146@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200010/124 X-Sequence-Number: 1786 "Franz J Fortuny" writes: > I have been using (with success) this SQL statement in PostgreSQL: > select col1, > case when col2 = true then > col3 > else > col4 > end as colw, > colM > where .... etc. > The above syntax, however, does not work for Interbase (6.01). CASE expressions are specified in SQL92, but they're labeled as an "intermediate SQL" feature rather than an "entry SQL" feature. So I'm not surprised that some other DBMSes don't have them. Entry SQL is a pretty impoverished subset (no VARCHAR type, to take a random example), so nearly everyone implements at least some intermediate- and full-SQL features. But exactly which ones is highly variable. regards, tom lane