Received: from forward.airstreamcomm.net (forward.airstreamcomm.net [64.33.128.12]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eBLHtW627024 for ; Thu, 21 Dec 2000 12:55:32 -0500 (EST) (envelope-from jghasler@win.bright.net) Received: from hasler.dhh.gt.org (elk-ras1-cs-27.dial.airstreamcomm.net [64.33.137.29]) by forward.airstreamcomm.net (8.9.3/8.9.3) with ESMTP id LAA19439 for ; Thu, 21 Dec 2000 11:55:13 -0600 (CST) Received: from [192.168.1.3] (helo=toncho.dhh.gt.org ident=mail) by hasler.dhh.gt.org with esmtp (Exim 3.12 #1 (Debian)) id 1499vm-0000KC-00 for ; Thu, 21 Dec 2000 11:55:06 -0600 Received: from john by toncho.dhh.gt.org with local (Exim 3.12 #1 (Debian)) id 1499vl-0007wo-00; Thu, 21 Dec 2000 11:55:05 -0600 To: PostgreSQL-SQL Subject: Re: Invoice number References: <00122111100003.25042@bering> <20001221095257.B5037@thune.mrc-home.org> From: John Hasler Date: 21 Dec 2000 11:55:05 -0600 In-Reply-To: Mike Castle's message of "Thu, 21 Dec 2000 09:52:57 -0600" Message-ID: <87puilr75y.fsf@toncho.dhh.gt.org> Lines: 17 User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Archive-Number: 200012/251 X-Sequence-Number: 588 Mike Castle writes: > If so, why is no rollbackable an issue? All you should need is unique > numbers. Not necessarily exactly sequential numbers. Sometimes business rules require that every member of a sequence of such things as invoice numbers be accounted for. Speculation: Would it be possible to log SERIAL's as they are issued? It might be sufficient to just record the user id, though it would be more useful to log some indication of what the number was used for (or at least whether or not it was used at all). -- John Hasler john@dhh.gt.org (John Hasler) Dancing Horse Hill Elmwood, WI