SQLite may throw the following error:
Expression tree is too large (maximum depth 1000)
When using PHP PDO with SQLite, the error messages sometimes are not really self-explaining. Today I had an error stating "bind or column index out of range". The "column index" part made me check the tables index and data type.
When developing apps by using SQLite as a storage backend, you most likely will sometime get the error message:
The message very clearly describes what happened: you have prepared an SQL statement like "SELECT ... WHERE id=? OR id=? OR id=?" or at least something like that, and the placeholders (in this case the question marks) are too many.
Today I decided to provide a brief introduction into using SQLite compared to mySQL for PHP and webserver environments.
Traditionally mySQL is first choice when developing a dynamic website with PHP. Recently SQLite is another database system (I intentionally don't call it a database server, see below for reasons why) getting very popular. SQLite has two main usage areas: Webservers (mainly with little performance requirements) and applications.
In this quick article I'd like to comment a special case which is very much undocumented yet.
Zend_Date is a mighty class for handling date and time. As for all of such mighty tools, there is a heavy downside: it's really expensive at runtime. Using a Zend_Date instance a few times is no big deal, but using a hundred instances and generating thousands of ISO-style dates and times may take several seconds.
Today I eventually started optimizing the performance (thereby reducing server load a bit). It appeared some pages of my larger websites have grown to round about 300 kb causing some latency for lower bandwidth visitor. Having a quite good connection myself, I didn't care about that much in the past. But that's ab pity, because it is very simple to add compression to pure PHP-generated content.
Bing is the latest remake of Microsoft's search engine. Since letdown live.com was closed, people start talking about the new search engine.
Google invented a tag called "nofollow" to give webmasters better controll about how a site spreads its link power. In this article I'll describe in detail how this tag works and how you can benefit from it. It contains some secret information about how Google handles links and Nofollow.
This seems to be a very special day. I don't remember if this ever happened to me, but this morning several Google services seem to be broken down for some reason. I'm unable to connect to Adsense or Adwords for about 1 1/2 hour now. The Google search engine and Google Analytics still work, so it's no general Google infrastructure break down.