From: Foster, Stephen <stephenlfoster@comcast.net>
To: pgsql-sql@postgresql.org
Subject: Trigger/Sequence headache
Date: Sun, 12 Feb 2006 16:27:48 -0600
Message-ID: <000801c63023$8e0af830$2101a8c0@cfgod> (raw)
This is going to be one of those stupid problems of mine. I have an
insert trigger setup to verify that duplicate or repeating information
isn't storage in the table. If trigger function finds the information
as a duplicate it returns a NULL and the information isn't added; that
works. The problem I'm having is that it is incrementing the sequence
counter even when the data isn't added. Is this something that I have
to live with or should I be returning something other than a NULL?
I have a function to re-sequence the table and reset the sequence
counter in another application. Normal for that application because of
the constant adding and deleting. So if there isn't another answer then
I can write a version of that for this application and run it
weekly/monthly depending on need and use. It just drives me nuts with
large holes in the table.
Thanks
Lee Foster/
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: stephenlfoster@comcast.net
Subject: Re: Trigger/Sequence headache
In-Reply-To: <000801c63023$8e0af830$2101a8c0@cfgod>
* 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