Received: from www.actarg.com (root@[209.180.91.25]) by hub.org (8.9.3/8.9.3) with ESMTP id AAA26026 for ; Wed, 30 Jun 1999 00:11:53 -0400 (EDT) (envelope-from kyle@actarg.com) Received: from actarg.com (kyle@tao.actarg.com [192.168.1.1]) by www.actarg.com (8.8.7/8.8.7) with ESMTP id WAA17547 for ; Tue, 29 Jun 1999 22:14:40 -0600 Received: (from kyle@localhost) by actarg.com (8.8.7/8.8.7) id WAA22152 for pgsql-sql@postgresql.org; Tue, 29 Jun 1999 22:11:50 -0600 From: Kyle Message-Id: <199906300411.WAA22152@actarg.com> Subject: begin/end/abort work for sequences? To: pgsql-sql@postgresql.org Date: Tue, 29 Jun 1999 22:11:49 -0600 (MDT) Content-Type: text I assumed that wrapping a call to nextval() in a transaction would allow me to roll back the update of the sequence. But when I do the following: begin; select nextval('po_seq'); abort; The sequence po_seq is advancing to the next value even though the transaction was aborted. If I put other things like updates, inserts, etc. inside the transaction, they seem to be rolled back OK, but not the update of the sequence. Am I doing something wrong? ---------------------------------------------------- Kyle Bateman President, Action Target Inc. "Viva Yo!" kyle@actarg.com (801)377-8033x101 ----------------------------------------------------