Karen:
Sounds a lot like Option #2, but with a high-performance permanent table. Hmm.
Bruce
-------- Original Message --------
Subject: [RBASE-L] - Re: Design Opinions Requested
From: [email protected]
Date: Thu, July 12, 2012 2:28 pm
To: [email protected] (RBASE-L Mailing List)
If a status history table is required, then the big problem is always determining what's
the latest status. My experience is that the view to get this is always a SLOW view
if you're doing anything other than a single-row lookup to it.
So what I've taken to doing (don't tell Cobb this) is I have been keeping history in
a table, and then using triggers on every update, insert, and delete to update a
"CurrentStatus" column in the main table so I can just search based on that!
Karen
In a message dated 7/12/2012 4:17:15 PM Central Daylight Time, [email protected] writes:
Our employee table uses a status history table since we have had many situations where an employee status changed several times.
The record with the null enddate is the active one.
