in reply to converting a large SGML file into a database

First a design question; why should it be in a database? SGML files are pretty well-defined and few applications need a lot of them.

Second: Being in a database suggests that a partial SGML file is good enough for most purposes. Perhaps. How do you keep them consistent?

Large file support is strictly up to the OS. Perl will usually accomodate itself to whatever the OS allows, so long as you compile your own perl.

After Compline,
Zaxo

  • Comment on Re: converting a large SGML file into a database

Replies are listed 'Best First'.
Re^2: converting a large SGML file into a database
by dannoura (Pilgrim) on Nov 19, 2005 at 11:53 UTC

    I decided to go for a database because the SGML file data structure is not the structure I want and also because I think a database would be faster for lookup (the next step in this script is converting the data to a hash of arrays so I have a hash lookup).

    I'm not sure I understand your second point. Once I convert the SGML file into a database I don't use the SGML file any more.

    Is there any reason to assume WinXP won't handle files of that size?

[reply]

In Section Seekers of Perl Wisdom