Re: too much OOP ?

1. For most of requests an RA description is close to optimal;

RA is proven to be very useful for common data management tasks.

2. SQL is the best way to spell RA requests.

No, it isn't. But it is the only availible way in current production
systems.

4. The non-functional requirements allow deployment of an SQL database as
the platform, or even as a component (and where is the rest?) [Such as
memory constraints, real-time constraints, mobile distributed components,
lag and blackout periods, security, safety etc]

True. Current mainstream SQL databases targets "business
applications". But there also exists embedded databases which target
applications in other areas. But obviously there are areas which is
not covered by current database implementations.

Any or all of these four assumptions can be wrong. As I said, I know
nothing about inventory management, but in my area of interest relational
view does not deliver.

I think you should have made this disclaimer from the beginning. I
agree with your that point 4 is a valid argument for not using SQL
databases, in some scenarios. But you have been extensivly arguing
that relational databases has basic flaws and that other libraries
could be successfully used instead of SQL databases, without limit the
claims to "my area of interest".

"Relational view does deliver" is pretty much true, since the none of
the mainstream SQL databases could be considered as relational (http://
myitforum.com/cs2/blogs/dhite/archive/2006/09/10/Codd_2700_s-12-Rules-
For-The-Relational-Model.aspx).

As for other things, I am dying to see a UI written in SQL...

SQL is a perfect language for reading and writing the GUI data. Lets
say you have a combo box. Just write a select statement returning the
data in the combo.

Also the GUI layout could easily be described using relations,
although many of current products used an obsolete hierarchic data
model (HTML).

//frebe
.

Relevant Pages

  • Re: Business objects, subset of collection
    ... SQL databases sucks for searching large data sets, ... client/server model, and thin clients. ... Lets say you want to find all unpaid invoices. ...
    (comp.object)
  • Re: XMLPropWorks changes question
    ... XML databases ... utilizing SQLite instead of a full blown client/server SQL system ala ... What's the opinion of those out there in the know about SQL databases? ... A beta version of XPW available for testing in a couple of weeks. ...
    (comp.cad.solidworks)
  • Re: Object/Relational Mapping is the Vietnam of Computer Sci
    ... Could you spare just a moment to give me your opinion on which way to go? ... One *cannot* rationally say that "I think relational databases ... fashion, hype, or religion over science and knowledge. ... lot of people start looking at other options than SQL databases ...
    (comp.lang.ruby)
  • Re: Object/Relational Mapping is the Vietnam of Computer Sci
    ... One *cannot* rationally say that "I think relational databases ... fashion, hype, or religion over science and knowledge. ... lot of people start looking at other options than SQL databases ... system vendors, who are part of the hype machine and are just as ...
    (comp.lang.ruby)
  • Re: custom data warehouse in python vs. out-of-the-box ETL tool
    ... Bill Inmon's "Building the Data Warehouse" is 17 ... My experience is that if you enjoy hacking around databases and are ... I had a server for each production DB, ...
    (comp.lang.python)