HI,
1. You can try to create a trigger before insert to check if the new row
exists in the table and if it does to cancel the insert.
2. Or create a UNIQUE INDEX on all the columns which will throw error if
you try to insert duplicate rows in the table.
Then in the apllication software just cat
Hi, TJ,
TJ O'Donnell wrote:
> So, is there a way (a constraint, a check?) that will simply
> REJECT a duplicate when I insert the raw data directly into x
> rather than FAILING on an error as it does
> with the unique constraint above?
Failing on an error is exactly the way PostgreSQL (and the S
I noticed this one by searching in the
archives, as I am working with some “optional” parameters myself
and noticed your solution. I just wanted to make one improvement suggestion
which is instead of checking whether or not a parameter has been used simply
start your query like so
Quer
Curtis Scheer wrote:
> I noticed this one by searching in the archives, as I am working with
some
> "optional" parameters myself and noticed your solution. I just wanted to
> make one improvement suggestion which is instead of checking whether
or not
> a parameter has been used simply start yo
