Re: COBOL and DB2 vs. Java and DB2

On 17 Sep, 17:30, "Pete Dashwood" <dashw...@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

Just one such is the emerging technology of Query Expressions (LINQ) and
Lambda functions for data, which is using the Relational model to set SQL on
its head and support deferred execution, load levelling across servers, and
parallel processing, all transparent to the application programmer. Some of
this stuff (Lambdas) is showing incredible data transfers with terabytes
transmitted instantly across country. (Try GOOGLE on the terms I've
mentioned.)

My pedanticism knows no bounds. Even at the speed of light it would
not be possible to transfer even one terabyte of data across country
INSTANTLY. You may care to try transferring one bit of data if you use
entangled photons but you that is one bit only.


Here's a video interview from 2005 with Anders Hejlberg, which explains why
an Object approach to Data access can allow "across the board" access to
tables in memory, XML files, Documents, as well as Relational DBs, using a
single OO Query language. Most of what he talks about is now available:http://channel9.msdn.com/showpost.aspx?postid=114680

If you bring yourself up to date on database technology you may well find it
blows the doors off traditional approaches...:-)


This brings to mind the existance of Cache (OO database for Java) and
the post above. Why would somebody want to use DB2 with Java when
there are better database technologies optimised for use with Java?

Personally, I find it very exciting and am beginning to use C# to run Query
Expressions rather than SQL. It is very early days yet and I am still
learning, but it is much more natural than SQL., and integrates seamlessly
into the language.


My boozy chum came out with a good comment about SQL and DB2. He
wondered why commercial use SQL was so difficult to understand?

- Show quoted text -


.

Relevant Pages

  • Re: Databinding - Best Practice (object-oriented)
    ... >>relational model throughout your application severely restricts the ... The Relational Model is not SQL. ... difficult to persuade developers to ditch the database independance this ... What SQL domains should be but they are not. ...
    (microsoft.public.dotnet.framework.windowsforms.databinding)
  • Re: Databinding - Best Practice (object-oriented)
    ... >>relational model throughout your application severely restricts the ... The Relational Model is not SQL. ... difficult to persuade developers to ditch the database independance this ... What SQL domains should be but they are not. ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: COBOL and DB2 vs. Java and DB2
    ... Lambda functions for data, which is using the Relational model to set SQL ... This brings to mind the existance of Cache (OO database for Java) and ...
    (comp.lang.cobol)
  • Re: OO vs. RDB challenge
    ... in practice its outweighed by the unfortunate fact that SQL ... > The Relational Model is the best possible layer, ... constraints of the RDBMS" is an attractive idea in theory, ... RDBMS in some other language and show its as easy as using an RDBMS". ...
    (comp.object)
  • Re: The best elegant solution to override 65k rows limit in a sheet
    ... >through heavy customization of business apps (i mention SAP, Oracle, ... >Peoplesoft etc...). ... >YOU ACTUALLY THINK THAT THE RELATIONAL MODEL LETS YOU DOWN BECAUSE YOU ... in the real world we have SQL. ...
    (microsoft.public.excel)