| From: | Dan Jewett <danjewett(at)mac(dot)com> |
|---|---|
| To: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: function does not exist error... |
| Date: | 2002-11-22 18:05:11 |
| Message-ID: | p05200f06ba04218fd466@[162.84.132.56] |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
>Dan,
>
>> 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
>> tables.
>>
>> 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.
>
>--
>-Josh Berkus
You are right of course. Thanks for rearranging my thinking on this.
So, on to figuring out the query for the batch.
Dan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dan Jewett | 2002-11-22 18:33:37 | |
| Previous Message | Tom Lane | 2002-11-22 16:41:38 | Re: How does "SELECT ... FOR UPDATE" work? |