in reply to Re: plsql vs. perl vs. neither and API's (code)
in thread plsql vs. perl vs. neither and API's (code)

MySQL is very fast..as long as you don't need the features left out to make it fast, and as long as the amount of data you are dealing with at once does not exceed RAM limits. See DBI + 'SELECT *' - Memory Use Galore? for more on the latter issue and, of course, Why not MySQL for more on the former.

Use the best tool for the job. MySQL is a great tool for some purposes. But it has limits and if you are going to advocate it, you should know what those limits currently are.

  • Comment on Re (tilly) 2: plsql vs. perl vs. neither and API's (code)

Replies are listed 'Best First'.
Re: Re (tilly) 2: plsql vs. perl vs. neither and API's (code)
by aquacade (Scribe) on Jul 30, 2001 at 06:09 UTC
    Thankfully, I've never had this problem because all my Windows workstation have at least 384MB of RAM and my tables in MySQL are all under 3M rows thus far. Please keep making comments and connections like this tilly for us all! The thread you mention is VERY valuable to me. I haven't had time (as yet) to search and read the entire corpora of Perl Monks knowledge. I'm still sloshing through current stuff trying to be more helpful than harmful. Thankfully Monks like you are there to balance my experiences with your Wisdom!

    ..:::::: aquacade ::::::..

[reply]

In Section Meditations