Re: too much OOP ?

On Fri, 4 Jan 2008 02:06:31 -0800 (PST), frebe wrote:

Others
quietly create their *libraries*. They might call them "engine",
"middleware", "framework", but show nothing alike that manic disorder the
former suffer... (:-))

What libraries are you suggesting instead of a SQL database? Please
show me some example.

There exist lots of container libraries.

Please point out one library that could be used instead of a SQL
database for an inventory management application?

As I said, write the requirements. The problem of you and the OP is that
you don't care to write the requirements down. Instead of that you think in
terms of DB records, i.e. an implementation. The rest follows. In OO one
would first identify and describe the things and only then say, "hey, that
looks much like a relation!"

What do you think of Tutorial D?

Too much C to my taste. I admire the Third Manifesto, but I consider it
rather as a home work for relational guys to do, before they teach the rest
of the world. Let's see how it will evolve.

Now I have a question to you. Why don't you implement RA (as it has to be
in your opinion) at the library level in some decent OOPL?

Actually I once did (http://butler.sf.net). But later I realized that
I was just reinventing the wheel (that wasn't really round). Using SQL
directly is far more powerful than building a complex class model.

Huh, know what? Nobody needs a class model of cr*p (read SQL). A model of
cr*p is itself cr*p. There is the ODBC mess for those who like such things.
You promised me clean RA instead.

Make it in
several variants with concurrency and persistency support as options. I bet
OO folks will embrace it.

If this should be done without a database back-end, you are simply
writing a new database engine.

I don't care about back-ends. I want to see the interface of. How do you
implement it, is not my business.

That dead DB horse you'll sell to no one.

Are your observation of the current software industry, that SQL
databases are dead?

You know, there is [economical] life after death... (:-))

--
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de
.

Relevant Pages

  • Re: too much OOP ?
    ... There exist lots of container libraries. ... Please point out one library that could be used instead of a SQL ... If this should be done without a database back-end, ... instead of a relational database, and that would be useful for example ...
    (comp.object)
  • Re: Viewing New Documents
    ... Pricey but nice. ... Create a SQL View on the database that goes through all the document ... Then create a Data View of that SQL View. ... Free but a pain (if you have a lot of document libraries and you have to ...
    (microsoft.public.sharepoint.windowsservices)
  • RE: Copy query between two separate databases using external ODBC link
    ... In query design view click on menu VIEW - SQL view and copy. ... query in the other database and go to the SQL view and paste. ... The file structure in both libraries is exactly the same, ...
    (microsoft.public.access.queries)
  • Re: Database Abstraction Layers / Frameworks
    ... On past projects in PHP4 I had always just written my own libraries to ... deal with database interaction. ... understanding the level of abstraction in all of these different ... abstraction and SQL abstraction I ...
    (comp.lang.php)
  • Re: dbdebunk Quote of Week comment
    ... > a lot of really bad SQL programmers. ... But SQL does not have a pointer data type or the ... > being told to design a database. ... But why is little Cindy Lou Who employee ...
    (comp.databases.theory)