Re: too much OOP ?
- From: frebe <frebe73@xxxxxxxxx>
- Date: Fri, 4 Jan 2008 02:06:31 -0800 (PST)
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?
I see no need in a special
language in order to implement RA at the library level.
Just show one example of a RA library, please.
There might exist
issues of making the syntax sugar sweeter (for returned tuples etc). But
that is irrelevant, after all SQL is far uglier than anything the most
poorly designed library could ever present...
I think we all agree that SQL isn't the most beautiful language. Even
if the standardization issue is important, I think there are room for
more than one family of relational languages. What do you think of
Tutorial D?
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.
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. If you are using a database back-end,
you are just putting a procedural interface on top of the database,
loosing a lot of the power with a 4GL. A lot of people have tried
making an OO interface on top of a relational database (Hibernate,
JDO, EJB, Rails) and they have not been very successful.
Why doesn't you show an OO API that could be used on top of, or
instead of a relational database, and that would be useful for example
inventory management applications.
That dead DB horse you'll sell to no one.
Are your observation of the current software industry, that SQL
databases are dead?
//frebe
.
- Follow-Ups:
- Re: too much OOP ?
- From: Dmitry A. Kazakov
- Re: too much OOP ?
- References:
- Re: too much OOP ?
- From: Daniel T.
- Re: too much OOP ?
- From: Dmitry A. Kazakov
- Re: too much OOP ?
- From: frebe
- Re: too much OOP ?
- From: Dmitry A. Kazakov
- Re: too much OOP ?
- From: frebe
- Re: too much OOP ?
- From: Dmitry A. Kazakov
- Re: too much OOP ?
- From: frebe
- Re: too much OOP ?
- From: Dmitry A. Kazakov
- Re: too much OOP ?
- From: frebe
- Re: too much OOP ?
- From: Dmitry A. Kazakov
- Re: too much OOP ?
- From: frebe
- Re: too much OOP ?
- From: Dmitry A. Kazakov
- Re: too much OOP ?
- From: frebe
- Re: too much OOP ?
- From: Dmitry A. Kazakov
- Re: too much OOP ?
- Prev by Date: Re: too much OOP ?
- Next by Date: Re: too much OOP ?
- Previous by thread: Re: too much OOP ?
- Next by thread: Re: too much OOP ?
- Index(es):
Relevant Pages
|