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 eBLKge640122 for ; Thu, 21 Dec 2000 15:42:40 -0500 (EST) (envelope-from jghasler@win.bright.net) Received: from hasler.dhh.gt.org (elk-ras1-cs-148.dial.airstreamcomm.net [64.33.137.150]) by forward.airstreamcomm.net (8.9.3/8.9.3) with ESMTP id OAA15110 for ; Thu, 21 Dec 2000 14:42:19 -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 149CXV-00015s-00 for ; Thu, 21 Dec 2000 14:42:13 -0600 Received: from john by toncho.dhh.gt.org with local (Exim 3.12 #1 (Debian)) id 149CWq-00081u-00; Thu, 21 Dec 2000 14:41:32 -0600 To: PostgreSQL-SQL Subject: Re: Invoice number References: <200012211750.eBLHohP12000@linda.lfix.co.uk> <20001221130833.C5263@thune.mrc-home.org> From: John Hasler Date: 21 Dec 2000 14:41:31 -0600 In-Reply-To: Mike Castle's message of "Thu, 21 Dec 2000 13:08:33 -0600" Message-ID: <878zp9qzgk.fsf@toncho.dhh.gt.org> Lines: 19 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/257 X-Sequence-Number: 594 Mike Castle writes: > Client 3 comes along. Do they use invoice #1, out of order, or invoice > #3? It shouldn't matter, as long as every number is accounted for. Seems to me that a trigger could make a log entry every time the serial is incremented. Workable? > What happens in a paper world if a cup of coffee is spilt on some > invoices, and these precious items are thrown in the trash? They are returned to accounting with an explanatory note, the numbers are logged as "voided", and the spoiled forms are shredded. -- John Hasler john@dhh.gt.org Dancing Horse Hill Elmwood, Wisconsin