Stephen,
You don't need to use a seperate batch to clean up the table. As
Stephan pointed out, you can call nextval after you determine that the
new row isn't a duplicate.
In case you misunderstood what Stephan had suggested let me try to
explain what is happening.
When PostgreSQL receives an IN
Hi, Stephen,
Foster, Stephen wrote:
> That's what I thought was going to be the answer. I was just hoping I
> was making a mistake somehow. It's no big deal but I like things
> organized and hate giant holes.
>
> Ok, one more thing for one of the batch jobs. No problem I have a
> cleanup routi
Lee Foster/
-Original Message-
From: Stephan Szabo [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 12, 2006 5:11 PM
To: Foster, Stephen
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] Trigger/Sequence headache
On Sun, 12 Feb 2006, Foster, Stephen wrote:
> This is going to be one of those stupi
On Sun, 12 Feb 2006, Foster, Stephen wrote:
> 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 a
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. T
