Pierce wrote:
>
> Business logic is code that isn't implied by the data, and its the
> most custom to a program. [...]
>
> In practice you have to write some minimal "data logic" to deal
> with stuff like "Fullname = firstname+middlename+lastname+suffix".
> And I tend to write a bunch of "page logic", because I can't stand
> the typical WO UI where you have an insert button, a save button,
> and a delete button on the same page.
>
Umm, I guess whether or not you agree with this will depend on precise
semantics of what you mean by "business logic" and "implied by the data". If
you're going to include "Fullname" as something implied by the data, then
validation could conceivably be included too, and hence one might argue that
some of the "business logic" may be contained in constraints in property
values of entries in a database, or in relationships between them.
To illustrate this, an example from the new PWO2 course: an instance of
Person might have a driving license, and an age, however if they are under 16
(state/country dependent) they should not have a driving license. This
EO-level validation can readily be included in the custom code for "Person".
Best wishes,
mmalc.
