Re: Data Redundancy

Marshall Spight wrote:
> x wrote:
> >
> > Step 1 for "declarative":
> > Try to unambiguously specify what the constraints are using a declarative
> > language
> >
> > Step 1 for "procedural":
> > Try to unambiguously specify what the constraints are using a procedural
> > language
> >
> > Step 2 for "procedural":
> > Verify if your specification is really what you wanted
> >
> > Step 2 for "declarative":
> > Verify if your specification is really what you wanted
>
> This description ignores a whole host of difficulties associated
> with procedural constraint implementation that aren't present
> in the declarative case. Your phrasing is valid but glosses
> over the differences.
>
> With declarative constraints, you have to figure out their
> logical specification, and you can simply tell the system
> to execute the logical specification. With procedural, you
> still have to figure out the logical specification, even if
> you are less aware of doing so because this step is
> often mixed in with the procedural implementation. Just
> because you mix them doesn't mean it's not there.

Or maybe with declarative constraints you have to a) figure out what you want to happen (function) so you can b) translate that into the correct declarative programming language statements (data) that your constraint engine will use as input. However, with procedural constraints you simply figure out what you want to happen (function) and write it (function).

It's a perspective thing, perhaps? Received on Fri Feb 17 2006 - 16:34:01 CET