>> The big picture of what I'm trying to do is that I have large flat
>> file of records created with info about individual recordings
>> (songs). I want to split those out into appropriately referenced
>> I thought I could create a combination of rules and triggers to step
>> through the table (or a text file exported from it) and send the data
>> where it needs to go. Part of the process would be to check for
>> existing entries to prevent redundency. I also want be able to add
>> entries to join tables on the fly.
>Why do you want to use Triggers and Rules? Do you need to import this data
>from source daily? Even so, batch processing will be faster than executing a
>trigger for each row inserted.
You are right of course. Thanks for rearranging my thinking on this.
So, on to figuring out the query for the batch.
In response to
pgsql-novice by date
|Next:||From: Dan Jewett||Date: 2002-11-22 18:33:37|
|Previous:||From: Tom Lane||Date: 2002-11-22 16:41:38|
|Subject: Re: How does "SELECT ... FOR UPDATE" work? |