From: Joel Fradkin <jfradkin@wazagua.com>
To: 'Richard Huxton' <dev@archonet.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: getting duplicate number is there a
Date: Tue, 17 May 2005 08:31:46 -0400
Message-ID: <000501c55adc$640855e0$797ba8c0@jfradkin> (raw)
In-Reply-To: <42899927.9070801@archonet.com>
I actually had the same thought (a counter table, I might be able to add
fields to the location table, but we have several applications case is just
an example). I agree that is probably the safest way and it also fixes
another issue I have been having when a user wants to transfer a case to
another location.
I appreciate the ideas, I could probably safely lock the numbering table as
I would be afraid of locking the case table.
Joel Fradkin
I'd be tempted to have a case_numbers table with (year,location,max_num)
and lock/read/insert to that. Makes everything explicit, and means you
don't have to mess around with counts/substrings.
--
Richard Huxton
Archonet Ltd
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: jfradkin@wazagua.com, dev@archonet.com
Subject: Re: getting duplicate number is there a
In-Reply-To: <000501c55adc$640855e0$797ba8c0@jfradkin>
* 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