Received: from golem.jpl.nasa.gov (root@hectic-3.jpl.nasa.gov [128.149.68.205]) by hub.org (8.8.8/8.7.5) with ESMTP id LAA04393 for ; Tue, 25 Aug 1998 11:28:01 -0400 (EDT) Received: from alumni.caltech.edu (localhost [127.0.0.1]) by golem.jpl.nasa.gov (8.8.5/8.8.5) with ESMTP id PAA30692; Tue, 25 Aug 1998 15:32:44 GMT Sender: tgl@mythos.jpl.nasa.gov Message-ID: <35E2D91B.52E75E76@alumni.caltech.edu> Date: Tue, 25 Aug 1998 15:32:43 +0000 From: "Thomas G. Lockhart" Organization: Caltech/JPL X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.30 i686) MIME-Version: 1.0 To: Bruce Momjian CC: hackers@postgreSQL.org Subject: Re: [HACKERS] Open 6.4 items References: <199808250258.WAA02834@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > > > SERIAL type auto-creates sequence > > I won't have time to do this for v6.4. > This would be nice to have, so maybe we can jam it in. If it is not > 100% correct, we have a month to make it correct, right? OK, I've committed the SERIAL type support to the CVS tree: postgres=> create table test (x text, s serial); NOTICE: CREATE TABLE will create implicit sequence test_s_seq for SERIAL column test.s NOTICE: CREATE TABLE/UNIQUE will create implicit index test_s_key for table test CREATE postgres=> insert into test values ('one'); INSERT 894781 1 postgres=> insert into test values ('two'); INSERT 894782 1 postgres=> insert into test values ('three'); INSERT 894783 1 postgres=> select * from test; x |s -----+- one |1 two |2 three|3 (3 rows) postgres=> \d Database = postgres +------------------+----------------------------------+----------+ | Owner | Relation | Type | +------------------+----------------------------------+----------+ | postgres | test | table | | postgres | test_s_key | index | | postgres | test_s_seq | sequence | +------------------+----------------------------------+----------+ postgres=> select * from test; x |s -----+- one |1 two |2 three|3 (3 rows) postgres=> \d pqReadData() -- backend closed the channel unexpectedly. Whoops! Don't know why this is causing trouble, but it seems to be reproducible. Will look at it some more... - Tom