Received: from hp00086.ina.de (hp00086.ina.de [159.51.6.8]) by hub.org (8.8.8/8.7.5) with ESMTP id DAA23827 for ; Fri, 21 Aug 1998 03:30:23 -0400 (EDT) Received: from su00574 by coi.ina.de with SMTP (SMI-8.6/KO-1.0SUN) for hp00086 id JAA03411; Fri, 21 Aug 1998 09:32:16 +0200 Date: Fri, 21 Aug 1998 09:30:07 +0200 (MET DST) From: Holger Mitterwald X-Sender: mittehlg@su00574 To: k_ogorman@kompass.ie cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] CHECK and IN (Sets in general) - What's the story? In-Reply-To: <009CAFD5.71417C54.5@kompass.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 20 Aug 1998 k_ogorman@kompass.ie wrote: > Is there a known reason why the following definition fails > the parser at the IN keyword?: > > create table kev_test ( my_tag char check (my_tag in ('A', 'B', 'C'))); It isn't this worse at all :-) First, your syntax is not correct. Second, you can change the 'IN' Clause with several 'OR' clauses. The result would look like this: create table kev_test ( my_tag char) constraint tester check (my_tag = 'A' OR my_tag='B' OR my_tag = 'C'); If somebody has a solution for the 'IN' construction.... mail it! So long, Holger -------------------------------------------------------------------------------- Holger Mitterwald COI-D #### ##### ### CONSULTING FUER OFFICE COI GmbH Herzogenaurach # # # # UND INFORMATION Industriestrasse 1 - 3 # # # # MANAGEMENT GmbH D-91074 Herzogenaurach #### ##### ### Tel.: 09132/82-3811