Re: ID field as logical address
From: Kevin Kirkpatrick <kvnkrkptrck_at_gmail.com>
Date: Mon, 1 Jun 2009 10:17:00 -0700 (PDT)
Message-ID: <895891d5-fe55-478d-81d7-e984bc37fff9_at_r13g2000vbr.googlegroups.com>
Date: Mon, 1 Jun 2009 10:17:00 -0700 (PDT)
Message-ID: <895891d5-fe55-478d-81d7-e984bc37fff9_at_r13g2000vbr.googlegroups.com>
On Jun 1, 11:39 am, "Brian Selzer" <br..._at_selzer-software.com> wrote:
> "Kevin Kirkpatrick" <kvnkrkpt..._at_gmail.com> wrote in message
>
> news:670a228b-b752-47eb-b2e4-68c966c449d9_at_s31g2000vbp.googlegroups.com...
>
> > What is the poor HR person to do when Mary Smith returns from a week
> > long Vegas trip and reports that she'd gotten married on Monday and
> > divorced on Friday?
>
> That should be obvious: issue two updates in succession, one for each event.
Am I reading that right? You think the data entry person should enter, as a fact to the database, "Mary Smith is currently Married", at a time when Mary Smith is definitely not married? Received on Mon Jun 01 2009 - 19:17:00 CEST