RE: [SQL] Trigger question

From: Michael J Davis <michael(dot)j(dot)davis(at)tvguide(dot)com>
To: "'Adam H(dot) Pendleton'" <apendleton(at)vgsinc(dot)com>, pgsql-sql(at)hub(dot)org
Subject: RE: [SQL] Trigger question
Date: 1999-05-10 18:41:41
Message-ID: 93C04F1F5173D211A27900105AA8FCFC1454CC@lambic.prevuenet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

I would not store the last name in the employee_payroll table. I the
primary should be something like an employee_id. This would eliminate the
need to update the employee_payroll table every time an employee name
changes.

> -----Original Message-----
> From: Adam H. Pendleton [SMTP:apendleton(at)vgsinc(dot)com]
> Sent: Monday, May 10, 1999 11:38 AM
> To: pgsql-sql(at)hub(dot)org
> Subject: [SQL] Trigger question
>
> I have a dilema, and I'm not sure what the best way to go about solving it
> is. I have a table called employee_master, and a table called
> employee_payroll. The primary key for both tables is the employee name.
> It
> would be easy for me to set up a trigger that checked the master table
> when
> inserting into the payroll table to make sure the employee exists. My
> problem is this: The employee names are stored Last, First in both
> tables.
> The data file I am parsing to insert into the payroll table contains just
> the last name. Now I can make a trigger that uses a 'like' and checks the
> employees division as well to ensure that they are in the employee_master,
> but how do I update with just the last name? I don't want to insert, I
> need
> to be able to update the data in the row.
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Si hoc legere scis nimium eruditionis habes.
>
>

Browse pgsql-sql by date

  From Date Subject
Next Message Adam H. Pendleton 1999-05-10 20:32:09 plpgsql error
Previous Message Adam H. Pendleton 1999-05-10 17:38:29 Trigger question