Re: Windows Ada database support.

[Georg Bauhaus <sb463ba@l1-hrz.uni-duisburg.de>]

Ole-Hjalmar Kristensen <ole-hjalmar.kristensen@substitute_employer_here.com> wrote:
: He may just as well be thinking in terms of sets and relations. SQL is
: just a slightly clumsy way of conveying those thoughts to the DB
: engine :-)

Yes, thanks. I was thinking about one of those tiny little
everyday problems, and how to solve it and how to employ Ada
.Containers as "middleware". The problem:

 "Declare an ordered selection of objects. Make it available"

Objects may be either just fetched from the DB or they may be synthesized,
i.e. newly constructed from the DB (!), effectively establishing a type.
If a language supports EVAL, you can even construct the types at
at language level at run time.

Omitting the ordering issue, a SETL2 expression demonstrates a
non-SQL solution:

  result := { [foo, bar] :
     id in { R.key : R in S | R.key >= 100 and R.key <= 200 },
        bar = T(foo) | foo = id };

No trace of SQL, but I'm sure you can see the relation between
a SET programming language and SQL. Note the result set ;-)
This is working code, S and T are sets of tuples.
You may say that there are tuples and sets, iieek. But the in
computer programs you will have to work with some sort of
compound data at some level.
If you dislike the presence of tuples, ".key" is a selector.
R.key means the same as R(1).  This allows you to build interfaces
so you don't have to see the tuples.

Dmitry, what is your plan the other way round, i.e. how do you
make data related expressions for some nice higher level abstraction?


-- Georg