in reply to Large Constant Database in Text File

one of the prime reasons for using a relational database engine is to index fields so you can search quickly. the database engine takes care of caching blocks of the indexes etc., so it doesn't do a sequential scan. you haven't said what kind of searches you're doing on the fields, so i can't give a definite answer whether a database engine would realy benefit. complex searches that try to partially match fields usually can't use an index anyway. if the searches lend themselves to a initial screening, then you could use grep utility and output to a temp file that you then scan.
the hardest line to type correctly is: stty erase ^H
  • Comment on Re: Large Constant Database in Text File

Replies are listed 'Best First'.
Re^2: Large Constant Database in Text File
by Anonymous Monk on Sep 04, 2006 at 10:39 UTC
    Hi

    Thank you for asking for more info, rather then saying it has to be relational, relational, relational!!

    To use your terminology it looks like I am doing a complex search - the vast majority of searches we do (probably over 95%) are to partialy match fields.

    So if I have a field with this text in "Timbrals Theatre"

    then a search on "Tim" would be a match. The script also has a 'match whole words' option, which if activated would mean the search on "Tim" would fail, but a search on "Timbrals or Theatre" would match.

    From the context its ounds like teh relational solution would struggle here - is that right?

[reply]

In Section Seekers of Perl Wisdom