Request to remove some of my pages + ask confirmation for guidelines
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
I don't have time to say much --- dashing off to work you know -- but thanks for the change in tone. There is definitely some value in some of the handbook pages that were started. Always nice to see new people drinking the drupal kool-aide, even if it takes awhile to come around too. This brings me to a quick question about the culture (not technology) of drupal development documentation. One of the things some of us could have done in response was to actually edit the pages that were posted. In a wiki, this would be expected and encouraged, along with log notes on why the changes were made. I realized when I was reading these pages, I could have done that. Would that have been considered good or bad manners in the drupal community? On Aug 28, 2009, at 12:18 AM, Jean-Michel Pouré wrote:
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
David Metzler wrote:
This brings me to a quick question about the culture (not technology) of drupal development documentation. One of the things some of us could have done in response was to actually edit the pages that were posted. In a wiki, this would be expected and encouraged, along with log notes on why the changes were made.
A better place to discuss the Drupal doc culture in general is on the documentation list.... but as to your specific question:
I realized when I was reading these pages, I could have done that. Would that have been considered good or bad manners in the drupal community?
It is always good manners on drupal.org to edit doc pages that you find problems in. If you do not have time or permission to edit the doc page, the second best thing is to file an issue in the Documentation project issue queue. Terrible things to do include flaming the author, or posting your suggestions in a comment on the page. --Jennifer -- Jennifer Hodgdon * Poplar ProductivityWare www.poplarware.com Drupal, WordPress, and custom Web programming
On Fri, Aug 28, 2009 at 7:30 AM, Jennifer Hodgdon<yahgrp@poplarware.com> wrote:
queue. Terrible things to do include flaming the author, or posting your suggestions in a comment on the page.
Sorry, this is off-topic and should go to the docs list, feel free to ignore. But, I didn't know it was considered terrible to post suggestions in a comment. Maybe this should be noted on the comment form? I did find this http://drupal.org/node/14345 which suggests that some comments containing suggestions or corrections are ok. --mark
mark burdett wrote:
[...] I didn't know it was considered terrible to post suggestions [to handbook pages] in a comment. Maybe this should be noted on the comment form? I did find this http://drupal.org/node/14345 which suggests that some comments containing suggestions or corrections are ok.
We're working on revising those standards -- they're outdated, especially now that anyone can edit most doc pages. The problem is that the comments don't translate into the doc getting revised, and people don't generally scroll down a page to read the comments. --Jennifer -- Jennifer Hodgdon * Poplar ProductivityWare www.poplarware.com Drupal, WordPress, and custom Web programming
Le vendredi 28 août 2009 à 07:09 -0700, David Metzler a écrit :
This brings me to a quick question about the culture (not technology) of drupal development documentation. One of the things some of us could have done in response was to actually edit the pages that were posted. In a wiki, this would be expected and encouraged, along with log notes on why the changes were made.
Yeah. I think it is good behavior to edit the pages and try to collaborate. Some of my pages were edited and are now better. I think we could benefit from publishing a slow query log collector which would collect them server-side in the database. In PostgreSQL this is possible using a cron job loading CSV logs into the database. Therefore you can access and fix slow queries that are executed in the real life, not in cache. Kind regards, Jean-Michel
participants (4)
-
David Metzler -
Jean-Michel Pouré -
Jennifer Hodgdon -
mark burdett