On 31/12/2022 00:41, Dennis Lee Bieber via fpc-pascal wrote:
Well, I understand it was originally called SEQL, E for English, but
SEQUEL - Structured English QUEry Langauge.
At the time SQL was being developed, every database system had its own
proprietary programming language. Often these required macro preprocessors
to turn embedded queries into "native" programming language source.
The relational database model was originally a "view" of how to access
databases, be they hierarchical (everything was a tree structure descending
from the top-most database record) or network (lots of bidirectional
circular linked lists connecting records to each other).
Hmmm. So that explains a lot. "Relational" sounds like it was never
actually meant to be a database. And it shows ...
SEQUEL - by its very nature - must therefore encapsulate a lot of what
should really be in the database but, because of the laws of "least
common denominator", it has to provide itself because it can't guarantee
it's in the database.
So we're stuck with the worst of both worlds. A database that was never
intended to be one. And a language that is a massive layering violation
containing loads of functionality that should not be there ...
:-( :-( :-(
Cheers,
Wol
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
