Dear friends, First I would like to apologize for the flame-war about Drupal sending a query returning 21.000 rows and computing it in PHP and then escalating to Dries. I hope that my account will not be blocked and at the same time I admit it was an error to escalate.
But understand that I had no other choice because my issue were being closed and my Drupal site was going to explode under load and I did not know how to override this function. IMHO several Drupal users may have experienced several slowdows due to this SQL query. So let's end it with my apologies. On another front, I would like you to delete some of my pages, which are crap and do not meet Drupal quality level: http://drupal.org/node/559986 Was: PostgreSQL cast. Proved to be wrong. ::int was a no-op. http://drupal.org/node/559474 Was: Replace whenever possible LEFT JOINs with INNER JOINs The reason is that I found 1 query in my database which executes faster as an INNER JOIN. So you were right to point out there is no clear rule. This assumption was made when discussed several years ago with a PostgreSQL core developer in an SQL submit. This is not the case in 100%, so let us the SQL planner decide. I will continue my work writing; http://drupal.org/node/555514 I notice that sometimes the server is getting slow. I hope that this will not make my life miserable. I would like to use the name "MySQLism" to name some SQL extensions used by MySQL. This is not a criticism. I treat both databases on the same level and will call PostgreSQLism such things in PostgreSQL. If you don't like, please tell me and I will not use such vocabulary. Kind regards, Jean-Michel
signature.asc
Description: Ceci est une partie de message numériquement signée
