[Leaplist] coding - rdbms, revisions, and fks

[Jason Boxman]

On Monday 30 November 2009 11:33:55 pm Phil Barnett wrote:
> On Mon, Nov 30, 2009 at 11:32 PM, Phil Barnett <philb at philb.us> wrote:
<snip> >
> > If the person has a name change, you inactivate his old name record,
> > leaving it in place and activiate a new name record and start building a
> > history around that. Leave a pointer to the new name in the old record.
>
> And you might find it useful to have a rearward pointer, so leave a pointer
> to the old record in the new record. That way you can travel the chain both
> directions.

Interesting approach I had not considered.  I could clone the record and flag 
it historical, then modify the original so I don't need to update all the 
foreign keys pointing to it, all within a BEGIN COMMIT block.

I must consider this further.

Thanks Phil!

-- 

"Don't put it in your mouth." - Arctic Silver 5 Manual



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.