Ian Michael Gumby wrote:
> Art,
>
> Thanks for the response.
>
> First I'm trying to see if there's a trend toward "self-healing" databases.
<SNIP>
Gotcha.

>
> I mean today's buzzword is Hibernate to have persistence java objects... but
> does it scale?

Oh, heck no, it scales like a jagged stone on a choppy day. Maybe once or
twice in the shallows then straight to the bottom.

Art S. Kagel

Ian Michael Gumby wrote:
> "Art S. Kagel" <kagel@bloomberg.net> wrote in message
> news:449034C7.8000009@bloomberg.net...
>
>>Ian Michael Gumby wrote:
>>
>>>Art,
>>>
>>>Thanks for the response.
>>>
>>>First I'm trying to see if there's a trend toward "self-healing"
>>>databases.
>>
>><SNIP>
>>Gotcha.
>>
>>
>>>I mean today's buzzword is Hibernate to have persistence java objects...
>>>but does it scale?
>>
>>Oh, heck no, it scales like a jagged stone on a choppy day. Maybe once or
>>twice in the shallows then straight to the bottom.
>>
>
> Thats the thing.
> You introduce a conceptual tool that should make life easier. Yet life would
> truly be easier if they taught database principals to app developers.
>
> But hey what do I know? ;-)

Taught a seminar here at Bloomberg a few years ago (might be time to repeat
it) on developing applications that use relational databases. One big point
I made was to avoid persisting application objects in the database or
developing application objects that mirror database objects. It's REALLY
inefficient. From either having to delete and reinsert an object to
persist it (a common paradigm), to the overhead of determining, after the
fact that you have one in memory already, whether it's already in the
database and whether it's been modified in memory since it was
fetched/created, so you can decide whether to persist it before it goes out
of scope, to fetching b'jillions of items from a large number of tables so
we can load them all into MAPs and things so we can find them and relate
them to other objects loaded from other tables. Well you get the picture.

Better to start with a SQL statement that gets you the data you need and
wrap an object around it with methods for updating the components in a
transaction safe manner.

Then there's the "We don't need no stinking cursors!" crowd who want to load
the entire database into a scroll window object. OK, I've ranted enough for
one day (I hope).

Art S. Kagel