From: | "Karl O(dot) Pinc" <kop(at)meme(dot)com> |
---|---|
To: | Kenneth Downs <ken(at)secdat(dot)com> |
Cc: | Martin Winsler <martinwinsler(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: General Ledger db design |
Date: | 2007-02-26 17:52:53 |
Message-ID: | 1172512373l.24168l.2l@mofo |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 02/26/2007 11:41:18 AM, Kenneth Downs wrote:
>> You can also not allow new rows to be inserted if there
>> is already a batch row, thus the insertion of a
>> batch row "closes" the batch.
>
> Not sure what you mean, but you can in fact have any number of open
> batches, on the assumption that it is a multi-user system.
I'm saying why have a close flag at all? Why not signal the
close of the batch by the creation of the batch row?
Karl <kop(at)meme(dot)com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2007-02-26 17:53:34 | Re: [GENERAL] PostgreSQL on Windows Paper |
Previous Message | Kenneth Downs | 2007-02-26 17:41:18 | Re: General Ledger db design |