Re: text parsing
- From: Carolyn Marenger <cajunk@xxxxxxxxxxxx>
- Date: Tue, 22 Jan 2008 08:13:34 -0500
McKirahan wrote:
"Carolyn Marenger" <cajunk@xxxxxxxxxxxx> wrote in messageA few answers
news:74fb1$479501d1$cf70133e$7458@xxxxxxxxxxxx
Can someone point me in the direction of some good documentation on text
parsing?
I want to take a bunch of text files (rtf), read them in and dump the
contents in a database. The files are effectively a flat file database,
with I suspect some fairly intricate programming needed to process the
files. Unfortunately, they are laid out for human readability, not data
conversion.
A few questions.
How many is a "bunch"?
What would the target database be -- MySQL?
What table and column structures do you envision?
Perhaps simply a single table with two columns:
filename (key) and a memo field containing the data?
What is the purpose behind doing this?
A bunch is about a dozen. Basically one large file that was broken into sixteen subsets, following the initial letter for each record.
The target database would be MySQL
I haven't looked too closely at the data, but I think one main table with a few linked tables for those cases where there may be more than one piece of data for a category. There are about 25 categories to each record. Eventually there would be additional structure added around the imported data, but that isn't relevant to importing the data itself. (I will confirm this before beginning to code.
The purpose: I am a D&D fan and I run games. I would like to be able to reference the material and automate much of the process so I don't have to lug and reference 20lbs of books.
Thanks, Carolyn
.
- Follow-Ups:
- Re: text parsing
- From: McKirahan
- Re: text parsing
- References:
- text parsing
- From: Carolyn Marenger
- Re: text parsing
- From: McKirahan
- text parsing
- Prev by Date: Re: IP Spoofing
- Next by Date: Re: text parsing
- Previous by thread: Re: text parsing
- Next by thread: Re: text parsing
- Index(es):
Relevant Pages
|