Re: the relational model of data objects *and* program objects
Date: Fri, 15 Apr 2005 14:51:01 GMT
Message-ID: <pxQ7e.10104$44.1312_at_newsread1.news.atl.earthlink.net>
> This is why the One True Data Dictionary must exist outside of all of
them,
> and be used to implement all of them. If the spec is both
> machine-readable and human-readable, mores the better.
PMFJI. This may have been covered already elsewhere in the discussion. If
so, my apologies.
I'm playing around with the idea of a programming language that combines the
functionality of traditional programming,
library function invocation, and data exchange with database servers and/or
user interface servers. In this concept,
SQL becomes the OUTPUT of a compiler, instead of the input to a compiler.
That is, you have a language in which code "makes sense", and is unified.
The compiler figures out which things should be coded to run on, say, a
Java Virtual Machine, which things should be resolved by library function
calls, and which things should be recoded as SQL style exchanges with
external servers.
I know this isn't exactly the direction you are going in. But maybe there's
a useful synthesis.
Received on Fri Apr 15 2005 - 16:51:01 CEST