Re: Having difficulty refactoring a DB application
From: Fredrik Bertilsson (fredrik_bertilsson_at_passagen.se)
Date: 10/12/04
- Previous message: Shayne Wissler: "Re: largest storage"
- In reply to: Daniel Parker: "Re: Having difficulty refactoring a DB application"
- Next in thread: Daniel Parker: "Re: Having difficulty refactoring a DB application"
- Reply: Daniel Parker: "Re: Having difficulty refactoring a DB application"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 11 Oct 2004 22:09:11 -0700
"Daniel Parker" <danielaparker@spam?nothanks.windupbird.com> wrote:
> >SQL can also be the interface to other data sources, flat files
> > etc.
> >
> Not a terribly useful one, though. Byte streams and sets of tuples don't
> have a lot in common.
"Flat file" is not the same as "file". A flat file is a file
containing records separated by a newline. These kind of files is very
similar to a relational table.
> I doubt it, I don't find generated table classes that useful,
But don't you have a need for putting the data from the database into
some carrier in the host language? Anyway this the way database
programming has been done for 40 years.
> If your application requirements are that
> simple,
Every application that uses a database needs structures for keeping
and manuipulating the data from the database. You don't want to run an
update SQL immediately when you want to update a column value.
> you don't need generated anything, your app can be dynamic, adapting
> to the metadata present in the SQL result sets,
This solution is less type safe, but still possible.
> Besides, what's special about generated table classes? You
> can write SQL statement that can produce a valid relation.
Sorry, I don't follow you here.
> > OODBMS is failing badly
>
> True, a bad idea whose time is over, but I don't think Elliott was referring
> to database management systems in the part that you quote.
Maybe we should let Elliott speak for himself...
> Databases are about data, objects are about something else.
I thought objects are about data AND functionality. But obviously I am
wrong.
> It isn't
> terribly useful in most cases to think of objects being mapped into tables,
> it just makes the objects look funny.
This is what O/R mapping is all about. Please tell the Hibernate
people that they are doing it all wrong...
> Think of data as being mapped into
> factories, and factories being used to create objects.
This looks funny... I have no idea what you are talking about. Can you
please give an example.
Fredrik Bertilsson
http://butler.sourceforge.net
- Previous message: Shayne Wissler: "Re: largest storage"
- In reply to: Daniel Parker: "Re: Having difficulty refactoring a DB application"
- Next in thread: Daniel Parker: "Re: Having difficulty refactoring a DB application"
- Reply: Daniel Parker: "Re: Having difficulty refactoring a DB application"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|