in reply to Re^2: Indexing two large text files
in thread Indexing two large text files
Granted... particularly in this case, I agree completely. A 350MB total-size file can simply fit in memory and be done with it. (I know that you have recently dealt with files that are several orders of magnitude larger.)
The notion of using an SQLite file, literally as a persistent index covering as many keys as may be necessary, is actually the one that I tend to come back to, over and over again, when dealing with files like these. I need to know where to find, via direct access, whatever it is I am looking for. One pass through the file locates everything. The “interesting stuff” now gets done with JOINs, often in a command-line ad hoc fashion. Not in the “gigantic” case you recently spoke of, but maybe a very useful idea in this one.
Not kosher to SQL tricks? And, (a mere...) 350 megs? “If you’ve got the RAM, then by all means use it and be done.” Perl won’t blink an eye.
| Replies are listed 'Best First'. | |
|---|---|
|
Re^4: Indexing two large text files
by BrowserUk (Patriarch) on Apr 09, 2012 at 22:14 UTC | |
by aaron_baugher (Curate) on Apr 10, 2012 at 15:15 UTC | |
by BrowserUk (Patriarch) on Apr 10, 2012 at 16:11 UTC | |
by aaron_baugher (Curate) on Apr 10, 2012 at 22:33 UTC | |
by BrowserUk (Patriarch) on Apr 11, 2012 at 03:55 UTC | |
| |
|
Re^4: Indexing two large text files
by never_more (Initiate) on Apr 10, 2012 at 11:57 UTC |