From: George Moga <george@cicnet.ro>
To: Mike Castle <dalgoda@ix.netcom.com>
To: pgsql-sql@postgresql.org
Subject: Re: Invoice number
Date: Fri, 22 Dec 2000 10:02:36 +0200
Message-ID: <3A430A9C.9C475E86@cicnet.ro> (raw)
References: <dalgoda@ix.netcom.com>
<200012211750.eBLHohP12000@linda.lfix.co.uk>
<20001221130833.C5263@thune.mrc-home.org>
Mike Castle wrote:
> What do you do on the following scenario:
>
> Client 1 is placing an order, gets invoice #1.
> Client 2 is simultaneously placing an order, and gets invoice #2.
>
> Client 1 changes mind and cancels order. Invoice #1 is not used. Invoice
> #2 is.
>
> Client 3 comes along. Do they use invoice #1, out of order, or invoice #3?
You must use invoice #3, because #1 was already used for another client and it
remain printed on paper.
I made an billing application (Tcl/Tk + PostgreSQL) and invoice numbers are
generated by a sequence. It works with multiple billing location. When an
operator generate an invoice, he work without a number ... the number is
generated in the moment of saving and printing. In this mode, is posible to
cancel a invoice before the number is generated and is imposible to duplicate
numbers.
When a numer is generated, operators can not cancel printing. In this case, one
number represent always one printed invoice. If the invoice is canceled, it's
"paper version" is canceled too.
> I suppose of the assignment of the invoice number is set up in such a way
> as it is the very last action performed just before the commit, you should
> be able to ensure that indeed the situation of having to deal with a
> rollback would never occur (outside of a system crash between assignment of
> invoice and commit, and that could be explained to auditors).
>
I use "begin transaction" ... "commit" (abort) in time to write positions in
invoice because I want to decrease (on increase) stocks on line. In this mode
the other uses get the real stock (I do not use a "stocks" table ... stocks are
calculated "on-line" ... sum(in)-sum(out) on that product for all prices who are
active at that moment) for the products who are in curent invoice. When invoice
is saved positions remain in database and is generated an invoice number or, if
invoice is canceled, all this position are deleted, stocks returns to original
values and no invoice number are generated.
>
> [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?]
>
I cancel all this invoices but I never thrown them to trash because, in ROMANIA,
printed invoces already have a printed number (with safety marks) and when
taxman came to check he want to see all this numbers, valids or canceled.
>
> mrc
> --
> Mike Castle Life is like a clock: You can work constantly
> dalgoda@ix.netcom.com and be right all the time, or not work at all
> www.netcom.com/~dalgoda/ and be right at least twice a day. -- mrc
> We are all of us living in the shadow of Manhattan. -- Watchmen
I hope this can help ...
Sorry for my poor english.
George Moga,
Data Systems SRL
Slobozia, ROMANIA
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: george@cicnet.ro, dalgoda@ix.netcom.com
Subject: Re: Invoice number
In-Reply-To: <3A430A9C.9C475E86@cicnet.ro>
References: <dalgoda@ix.netcom.com> <200012211750.eBLHohP12000@linda.lfix.co.uk> <20001221130833.C5263@thune.mrc-home.org> <3A430A9C.9C475E86@cicnet.ro>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox