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


good chemistry is complicated, and a little bit messy -LW
	PerlMonks

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

by tilly (Archbishop)

on Jul 30, 2001 at 05:45 UTC ( [id://100756]=note: print w/replies, xml )

Need Help??

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.