Re^2: Simple & convenient Perl database

Replies are listed 'Best First'.
•Re^3: Simple & convenient Perl database by merlyn (Sage) on Sep 22, 2004 at 16:12 UTC
What I need is freeware database PERL SCRIPT. All I need is change path to perl* and put script on web server.* It sounds to me like you're an end user, not a Perl programmer. In that case, you're probably asking this question in the wrong place, as The monastery is about supporting Perl programmers, not Perl end-users. Perhaps you could choose to become a programmer, or perhaps you should hire a programmer or consultant to finish your task, or find some sort of end-user support community. -- Randal L. Schwartz, Perl hacker Be sure to read my standard disclaimer if this is a reply.	[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.
Re^3: Simple & convenient Perl database by punkish (Priest) on Sep 22, 2004 at 16:18 UTC
Otherwise Perl is wrong tool Wrong tool for what? And what would you consider as alternative tools? Santander, you have to be more forthcoming with what you want and what you don't want. You wanted a free database, but you didn't specify that you didn't want to deal with DBI (hence, I am assuming, SQL). So, various wise monks recommended SQLite, and one even recommended DBD-CSV, but they all seem to not meet your requirements. These kinds of questions are not very helpful and waste everyone's effort. You also say that you want a "freeware database PERL SCRIPT." What do you want... a database, or a script? What do you exactly want to do? From your original post it seems that your text file is doing the work for you quite well, isn't it? 8847 rows, 10 columns are peanuts for a decent computer and Perl... no one will even know there is any processing going on. And since you also mentioned "Correct/update items online is not necessary" (whatever that means), a text file would be fine for you. Perl can happily munch through few tens of thousands of lines of text without any problems. If you start running into speed issues, you can think of converting to BerkeleyDB, but you haven't specified upfront if that is too "abtract" for you. Ask mostly exactly what you want, and also check out a recent article on perl.com regarding embedded databases. Hope all this helps.	[reply]