Sean Davis schrieb:

> Just keep in mind that the trigger runs on EVERY insert, even those for
> which the unique clause is not violated. If that is the behavior you need,
> then use the trigger. However, if you know that after you have clean data
> in the table, you will not be inserting "duplicates" (I think this is the
> typical case), then a trigger may not be the way to go.
>
These were my concerns in the first place I was thinking about using
triggers. Maybe I haven't really understood your suggestion right. When
would the temporary table be created? Isn't it neccessary to create it
on every insert, too? With wich statement could I do this without using
a trigger which is fired on every insert?

Thanks for your patience.

Regards,
Verena



---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Verena Ruff wrote:
> Sean Davis schrieb:
>
>> Just keep in mind that the trigger runs on EVERY insert, even those for
>> which the unique clause is not violated. If that is the behavior you
>> need,
>> then use the trigger. However, if you know that after you have clean
>> data
>> in the table, you will not be inserting "duplicates" (I think this is the
>> typical case), then a trigger may not be the way to go.
>>
>
> These were my concerns in the first place I was thinking about using
> triggers. Maybe I haven't really understood your suggestion right. When
> would the temporary table be created? Isn't it neccessary to create it
> on every insert, too? With wich statement could I do this without using
> a trigger which is fired on every insert?
>
> Thanks for your patience.

No problem. I was thinking that you had a bunch of data that you wanted
to load ONCE, clean up, and then you would NOT be inserting duplicated
values. If you are going to be inserting duplicates potentially with
every insert, I think that a trigger is the only way to go on the DB
side of things. Of course, you could do things on the client side, as
well (do a lookup, find nothing--do insert, find something--do nothing
or do update).

Sean

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Hi,

Sean Davis schrieb:
> No problem. I was thinking that you had a bunch of data that you
> wanted to load ONCE, clean up, and then you would NOT be inserting
> duplicated values. If you are going to be inserting duplicates
> potentially with every insert, I think that a trigger is the only way
> to go on the DB side of things. Of course, you could do things on the
> client side, as well (do a lookup, find nothing--do insert, find
> something--do nothing or do update).

Thanks for your opinion. Then I'll go with a trigger.

Regards,
Verena

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq