trq

The simplest way to gain request-start to request-end speed is to cache using something like akamai.

That is correct.

CodeIgnitor will teach you nothing.

Codelgniter is an abomination and a dying project so forget it. Any of the other 3 are probably worthwhile though I don't hear much about Cake these days (but that is likely just the circles I hang in). As for where to start. This question gets asked all the time and the answer is always the same. Try them all and see. If I were in your position I would spend a weekend with each, and then decide. They are all very capable, so it's just personal opinions as to which one you like best.

It is. I use it on a daily basis with a few large Symfony2 based applications. It's a great tool. http://thorpesystems.com/blog/debugging-php-in-vim I'm pretty interested in taking a look at http://phpdbg.com one of these days too as it ships with PHP5.6.

vim for Windows? Yuk.

We do not delete accounts. If you don't want it, don't use it, simple.

2 & 3 will never happen using vim's autocompletion. And 1, well, vim gets its context from a few different locations depending on the keystroke you use to start completion. Generally, I only ever use the context of the current buffer. This meens variables will only be completed if they already exist in the current buffer. Not that I use completion often anyway.

Not at all. That's why I said I rarely use it.

vim's code completion is the best (quickest and most flexible) Ive used, not that I use it often.

Silex (http://silex.sensiolabs.org) is an awesome micro-framework built on the shoulders of Symfony (another great though full stack framework).

$lstr needs to be the second argument to prepare() not query().

Post your current code.

WHERE ".S_DB.".wpSlug in(%s)"), $lstr);

Instead of using variables directly within your query, you use placeholders. You then pass your variables in as extra arguments to prepare().