Output to text files or a database?
- From: "kd" <KeeganDunn@xxxxxxxxx>
- Date: 1 Mar 2006 07:27:18 -0800
I was reading The Art of Unix Programming yesterday, and was inspired
to rework and split up an large monolithic application of mine.
This software has to do with the retrieval and processing of travel
information (flights, hotels, etc) from different sources. Each source
has travel data formatted differently.
With plain text files being the universally loved file format, I
planned on writing small apps that would pull down data from these
different sources, and write them to text files in a universal format.
Another small app would read these text files, generate sql insert
statements from the data, and dump all the data into a relational
database.
I proposed this to a coworker, and he asked why the text files were
even necessary -- why not just immediately generate sql statements from
the different formats, and use the tables in the DB as the universal
format? Textual representations of that data could just be generated
from the database, after all.
Is he right? Is there any reason to use text files as an intermediate
format? My gut is telling me to keep them, but my gut isn't good at
convincing people. :) What am I missing?
.
- Follow-Ups:
- Re: Output to text files or a database?
- From: Pascal Bourguignon
- Re: Output to text files or a database?
- From: Mark Rafn
- Re: Output to text files or a database?
- From: toby
- Re: Output to text files or a database?
- From: Gordon Burditt
- Re: Output to text files or a database?
- From: Robert Harris
- Re: Output to text files or a database?
- From: Lew Pitcher
- Re: Output to text files or a database?
- Prev by Date: IP_HDRINCL option is not supported with IPv6
- Next by Date: Re: Output to text files or a database?
- Previous by thread: IP_HDRINCL option is not supported with IPv6
- Next by thread: Re: Output to text files or a database?
- Index(es):
Relevant Pages
|