Re: By The Dawn's Normal Light

From: Dawn M. Wolthuis <dwolt_at_tincat-group.comREMOVE>
Date: Mon, 1 Nov 2004 19:20:42 -0600
Message-ID: <cm6nde$a6n$1_at_news.netins.net>


"Kenneth Downs" <firstinit.lastname_at_lastnameplusfam.net> wrote in message news:k3g6mc.e5b.ln_at_192.168.10.210...
> erk wrote:
>
> >
> > In other words, what I need is a relational expression language which
> > operates over my GUI and business data as nicely as it can over
> > "persistent" data, since it's all just data. The constraints keep me
> > honest, in a much more expressive and effective way than Java's assert
> > (which has some minimal uses), and even more than preconditions and
> > postconditions a la iContract (since relational constraints are over
> > one or more relations, not on a single class or method).
> >
>
> Let's say jave pulls down what we'll call an "EKDC", for "E"rk and "K"en's
> "D"iscussion "C"ursor. You execute some command like:
>
> EKD EKD1 = connection.Execute("Select * from table");
> // note no statement object
>
> Then perhaps:
>
> EKD.Command("update this set some_Column = " + blah");
> EKD.Push();
>
> Just a bunch of junk code, but meant to demonstrate the use of SQL
locally,
> what about that? Why invent a new format for Java?

And how did you know to make the GUI component an xyz component so that the user could select only valid values, for example? In other words, how is the GUI savvy to the business rules in your example? Either I'm missing something or you are with the example. --dawn

> --
> Kenneth Downs
> Use first initial plus last name at last name plus literal "fam.net" to
> email me
Received on Tue Nov 02 2004 - 02:20:42 CET

Original text of this message