Re: ID field as logical address
Date: Thu, 11 Jun 2009 10:46:58 -0700 (PDT)
Message-ID: <5875dfaa-415e-4e01-9bb2-228536be5356_at_j20g2000vbp.googlegroups.com>
On Jun 10, 10:14 pm, Kevin Kirkpatrick <kvnkrkpt..._at_gmail.com> wrote:
>
> If your data model does not allow for assertions about bin movement,
> then you cannot coherently enforce constraints on bin movement. In
> this case, the model doesn't support propositions of the form
> BIN_MOVEMENT {warehouse, row, shelf, bin, prior_warehouse, prior_row,
> prior_shelf, prior_bin [...,picker_number, movement_time,...] }
> (to be interpretted as: "The bin currently in <warehouse> in <row> on
> <shelf> labeled <bin> was moved there directly from <prior_warehouse>
> in <prior_row> on <prior_shelf> labeled <prior_bin> ...", or something
> similar). This is only needless clutter if the client is compared
> about the prior location of a bin (in which case, he can't sensically
> request a constraint referring to that property).
>
Hmm - must've been typing while distracted... this should read:
This is only needless clutter if the client is not concerned about the prior location of a bin (in which case, he can't sensically request a constraint referring to that property). Received on Thu Jun 11 2009 - 19:46:58 CEST