All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Please Log In to Continue

At least not against a good database. (eg Oracle, PostgreSQL, etc - but MySQL would be fine.)

The problem is that there is a trade-off between time spend preparing a query and query performance. It would not be inappropriate to think of preparing a query as a "compile and optimize this SQL" step. MySQL spends very little energy preparing, and therefore its ability to handle complex queries suffers. Most other databases put a lot of energy into preparing, and so it is very important to try to avoid recomp

Actually I am going to use it on a very very busy site;) SQL preparing does not make much sense for me since our platform will usually work in the context of PostgreSQL PL/Proxy cluster *AND* the query could be dynamic enough to defeat ordinary DBI param binding.

Actually runtime performance is the reason to choose source-filter solutions in the first place;)

Also, the SQL example is, well, merely an example...Filter::QuasiQuote's power reveals in the context of true DSLs;)

My experience says that with a sane design you can run one of the top couple thousand busiest websites on the internet on a handful of webservers, paying only a modest amount of attention to performance of the code on your webservers.

That same experience says that tiny mistakes in how you handle your database can cause that same site to melt unexpectedly.

The lesson is to not worry about webserver performance, but be paranoid about database performance. Which means use placeholders properly. If you do it d

I must say that all you say is indeed true for an ordinary web application:)

But unfortunately I can't use prepare+execute in my OpenResty platform in particular. Why? Because it must scale by design to serve lots of apps here in Yahoo! China and Alibaba. So it must be a cluster or something like that.

The PL/Proxy database server requires frontend queries to be of the following form: