From owner-pgsql-hackers@hub.org Tue Jun 1 22:31:18 1999 Received: from renoir.op.net (root@renoir.op.net [209.152.193.4]) by candle.pha.pa.us (8.9.0/8.9.0) with ESMTP id WAA09988 for ; Tue, 1 Jun 1999 22:31:17 -0400 (EDT) Received: from hub.org (hub.org [209.167.229.1]) by renoir.op.net (o1/$ Revision: 1.18 $) with ESMTP id WAA18944 for ; Tue, 1 Jun 1999 22:08:09 -0400 (EDT) Received: from hub.org (hub.org [209.167.229.1]) by hub.org (8.9.3/8.9.3) with ESMTP id WAA75604; Tue, 1 Jun 1999 22:01:31 -0400 (EDT) (envelope-from owner-pgsql-hackers@hub.org) Received: by hub.org (TLB v0.10a (1.23 tibbs 1997/01/09 00:29:32)); Tue, 01 Jun 1999 22:01:11 +0000 (EDT) Received: (from majordom@localhost) by hub.org (8.9.3/8.9.3) id WAA75519 for pgsql-hackers-outgoing; Tue, 1 Jun 1999 22:01:09 -0400 (EDT) (envelope-from owner-pgsql-hackers@postgreSQL.org) X-Authentication-Warning: hub.org: majordom set sender to owner-pgsql-hackers@postgreSQL.org using -f Received: from localhost.localdomain (h246.ozemail2.ozemail.com.au [203.108.14.246]) by hub.org (8.9.3/8.9.3) with ESMTP id WAA75452 for ; Tue, 1 Jun 1999 22:00:50 -0400 (EDT) (envelope-from chris.bitmead@bigfoot.com) Received: from bigfoot.com (localhost [127.0.0.1]) by localhost.localdomain (8.8.7/8.8.7) with ESMTP id KAA04059 for ; Wed, 2 Jun 1999 10:50:11 +1000 Message-ID: <37547FC3.40106A5E@bigfoot.com> Date: Wed, 02 Jun 1999 10:50:11 +1000 From: Chris Bitmead X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.6 i686) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-hackers@hub.org Subject: Re: [HACKERS] ALTER TABLE ADD COLUMN References: <199906011436.KAA23479@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-pgsql-hackers@postgreSQL.org Precedence: bulk Status: RO Bruce Momjian wrote: > Our TODO now has: > > * ALTER TABLE ADD COLUMN to inherited table put column in wrong place > > I don't think any of us understand the issues on this one. Let me guess at the problem. When you add a column, it doesn't change all the records, therefore the column must be added at the end. This means that the columns will not be in the same order as if you had created them from scratch. There seem to be three solutions: a) Go to a much more sophisticated schema system, with versions and version numbers (fairly hard but desirable to fix other schema change problems). Then insert the column in the position it is supposed to be in. b) Fix the copy command to input and output the columns, not in the order they are in, but in the order they would be in on re-creation. c) make the copy command take arguments specifying the field names, like INSERT can do. I think it would be good if Postgres had all 3 features. Probably (b) is the least work. From owner-pgsql-general@hub.org Fri Jul 9 04:01:16 1999 Received: from renoir.op.net (root@renoir.op.net [209.152.193.4]) by candle.pha.pa.us (8.9.0/8.9.0) with ESMTP id EAA22565 for ; Fri, 9 Jul 1999 04:01:15 -0400 (EDT) Received: from hub.org (hub.org [209.167.229.1]) by renoir.op.net (o1/$ Revision: 1.18 $) with ESMTP id DAA10238 for ; Fri, 9 Jul 1999 03:56:46 -0400 (EDT) Received: from hub.org (hub.org [209.167.229.1]) by hub.org (8.9.3/8.9.3) with ESMTP id DAA79895; Fri, 9 Jul 1999 03:53:13 -0400 (EDT) (envelope-from owner-pgsql-general@hub.org) Received: by hub.org (TLB v0.10a (1.23 tibbs 1997/01/09 00:29:32)); Fri, 09 Jul 1999 03:47:45 +0000 (EDT) Received: (from majordom@localhost) by hub.org (8.9.3/8.9.3) id DAA79076 for pgsql-general-outgoing; Fri, 9 Jul 1999 03:47:43 -0400 (EDT) (envelope-from owner-pgsql-general@postgreSQL.org) X-Authentication-Warning: hub.org: majordom set sender to owner-pgsql-general@postgreSQL.org using -f Received: from ns.idianet.net ([195.154.201.1]) by hub.org (8.9.3/8.9.3) with ESMTP id DAA79054 for ; Fri, 9 Jul 1999 03:47:37 -0400 (EDT) (envelope-from haj@idianet.net) Received: from kosovo (ppp150-paris2.isdnet.net [194.149.182.150]) by ns.idianet.net (8.9.1/8.9.1) with SMTP id JAA08143; Fri, 9 Jul 1999 09:43:35 +0200 (CEST) Message-ID: <000c01bec9df$3704bd20$0601a8c0@kosovo.idianet.net> Reply-To: "Jonathan davis" From: "Jonathan davis" To: "Bruce Momjian" Cc: "Pgsql-General@Postgresql. Org" Subject: Re: [GENERAL] just little BUG Date: Fri, 9 Jul 1999 09:46:42 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-pgsql-general@postgreSQL.org Precedence: bulk Status: ROr >[Charset iso-8859-1 unsupported, filtering to ASCII...] >> hello all >> >> normaly a UNIQUE PRIMARY KEY is unique but >> when you use a heritage, you can insert a duplicate key !!!! > >I assume you mean inheritance. > >Can you send us a little test sample please? > >-- hello all this is the problem: example: test=> CREATE TABLE MAN(name char(10) UNIQUE PRIMARY KEY);T test=> CREATE TABLE PROFESSOR(scool char(20))INHERITS(MAN); test=> INSERT INTO PROFESSOR(name) VALUES('DAVIS'); INSERT 54424 1 test=> INSERT INTO PROFESSOR(name) VALUES('DAVIS'); INSERT 54425 1 From owner-pgsql-hackers@hub.org Tue Apr 20 10:34:34 1999 Received: from hub.org (hub.org [209.47.145.100]) by candle.pha.pa.us (8.9.0/8.9.0) with ESMTP id KAA28480 for ; Tue, 20 Apr 1999 10:34:31 -0400 (EDT) Received: from localhost (majordom@localhost) by hub.org (8.9.3/8.9.1) with SMTP id KAA12281; Tue, 20 Apr 1999 10:33:22 -0400 (EDT) (envelope-from owner-pgsql-hackers@hub.org) Received: by hub.org (TLB v0.10a (1.23 tibbs 1997/01/09 00:29:32)); Tue, 20 Apr 1999 10:32:04 +0000 (EDT) Received: (from majordom@localhost) by hub.org (8.9.3/8.9.1) id KAA11432 for pgsql-hackers-outgoing; Tue, 20 Apr 1999 10:32:01 -0400 (EDT) (envelope-from owner-pgsql-hackers@postgreSQL.org) Received: from tech.com.au (IDENT:root@techpt.lnk.telstra.net [139.130.75.122]) by hub.org (8.9.3/8.9.1) with ESMTP id KAA11378 for ; Tue, 20 Apr 1999 10:31:52 -0400 (EDT) (envelope-from chris.bitmead@bigfoot.com) Received: from bigfoot.com (chris@localhost [127.0.0.1]) by tech.com.au (8.8.7/8.8.7) with ESMTP id AAA21255 for ; Wed, 21 Apr 1999 00:31:32 +1000 Message-ID: <371C8FC3.4804CF87@bigfoot.com> Date: Tue, 20 Apr 1999 14:31:31 +0000 From: Chris Bitmead X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: hackers@postgreSQL.org Subject: Re: [HACKERS] Heads up: does RULES regress test still work for you? References: <199904151054.UAA07367@tech.com.au> <3715C69E.AE517ADB@bigfoot.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-pgsql-hackers@postgreSQL.org Precedence: bulk Status: RO Does the following indicate a bug? It sure is wierd. Maybe some of these statements aren't supported by postgresql (??), but the outcome doesn't make sense to me. httpd=> CREATE TABLE x (y text); CREATE httpd=> CREATE VIEW z AS select * from x; CREATE httpd=> CREATE TABLE a (b text) INHERITS(z); CREATE httpd=> INSERT INTO x VALUES ('foo'); INSERT 168602 1 httpd=> select * from z*; y --- foo foo (2 rows) How did we suddenly get two rows?? -- Chris Bitmead http://www.bigfoot.com/~chris.bitmead mailto:chris.bitmead@bigfoot.com From owner-pgsql-hackers@hub.org Tue May 25 11:01:16 1999 Received: from renoir.op.net (root@renoir.op.net [209.152.193.4]) by candle.pha.pa.us (8.9.0/8.9.0) with ESMTP id LAA15867 for ; Tue, 25 May 1999 11:01:16 -0400 (EDT) Received: from hub.org (hub.org [209.167.229.1]) by renoir.op.net (o1/$ Revision: 1.18 $) with ESMTP id KAA10712 for ; Tue, 25 May 1999 10:55:17 -0400 (EDT) Received: from hub.org (hub.org [209.167.229.1]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA07206; Tue, 25 May 1999 10:45:50 -0400 (EDT) (envelope-from owner-pgsql-hackers@hub.org) Received: by hub.org (TLB v0.10a (1.23 tibbs 1997/01/09 00:29:32)); Tue, 25 May 1999 10:43:02 +0000 (EDT) Received: (from majordom@localhost) by hub.org (8.9.3/8.9.3) id KAA06706 for pgsql-hackers-outgoing; Tue, 25 May 1999 10:43:01 -0400 (EDT) (envelope-from owner-pgsql-hackers@postgreSQL.org) X-Authentication-Warning: hub.org: majordom set sender to owner-pgsql-hackers@postgreSQL.org using -f Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA06690 for ; Tue, 25 May 1999 10:42:57 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA02984 for ; Tue, 25 May 1999 10:42:39 -0400 (EDT) To: pgsql-hackers@postgreSQL.org Subject: [HACKERS] INSERT INTO view means what exactly? Date: Tue, 25 May 1999 10:42:39 -0400 Message-ID: <2981.927643359@sss.pgh.pa.us> From: Tom Lane Sender: owner-pgsql-hackers@postgreSQL.org Precedence: bulk Status: ROr With current sources: regression=> CREATE TABLE x (y text); CREATE regression=> CREATE VIEW z AS select * from x; CREATE regression=> INSERT INTO x VALUES ('foo'); INSERT 411635 1 regression=> INSERT INTO z VALUES ('bar'); INSERT 411636 1 regression=> select * from x; y --- foo (1 row) regression=> select * from z; y --- foo (1 row) OK, where'd tuple 411636 go? Seems to me that the insert should either have been rejected or caused an insert into x, depending on how transparent you think views are (I always thought they were read-only?). Dropping the data into never-never land and giving a misleading success response code is not my idea of proper behavior. regards, tom lane