Subj : Re: Change Patterns (was: Polymorphism sucks)
To   : comp.programming,comp.object
From : CBFalconer
Date : Sat Jul 02 2005 04:11 am

Chris Sonnack wrote:
> topmind writes:
> 
.... snip ...
>>
>> And that is not an uncommon need. Often one cannot know
>> future uses of a given set of information at the start
>> of a project.  Thus, DB's are a good future-change hedge.
> 
> In fact, any time one is dealing with a substantial dataset,
> a DB is probably a good choice.  And they're an obvious
> choice if you need to persist data between program runs.
> 
> However, at a guess, the bulk of programming problems do
> not lie in that domain.

Having cut this monster (even without EGN inflation) down to
something where I think I can inject a comment, it is often useful
to think of an application as creating, populating, using, and
destroying a database.   An example of this is my id2id program,
which uses hashlib as the database mechanism.  It reads in a list
of ids, populates a database which has two related tables, and then
uses that database to process all the files.

Databases do not have to be disk based.  You can see the id2id
program at:

  <http://cbfalconer.home.att.net/download/id2id-20.zip>

-- 
"If you want to post a followup via groups.google.com, don't use
 the broken "Reply" link at the bottom of the article.  Click on 
 "show options" at the top of the article, then click on the 
 "Reply" at the bottom of the article headers." - Keith Thompson

.