<br><br><div class="gmail_quote">On Jan 21, 2008 7:42 AM, Jean-Michel Pouré <<a href="mailto:jm@poure.com">jm@poure.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Dear friends,<br><div class="Ih2E3d"><br>> That is all well and good from "it runs" ( i.e. unit testing,<br>> functionality is OK),<br>> but when you try to optimize for large datasets or complex queries,
<br>> you often<br>> have to do things that are database engine specific.<br>><br>> This is a classic clash been theory and reality.<br><br></div>Sorry, not my opinion.<br>MySQL employs non-standard SQL queries.
<br><br>If the code was written primarily for PostgreSQL using tables,<br>standard sql queries and views, it would run smoothly on MySQL and most<br>databases like Oracle and DB2.<br><br>This is because PostgreSQL is the standard SQL99 implementation.
<br>Very few things differ in PostgreSQL.<br><br>The converse is not true.<br><div class="Ih2E3d"></div></blockquote><div><br>That is all good, but how is that related to the issue at hand? We have<br>a problem as it is with development and testing resources for PostgreSQL,
<br>so your solution is to make everyone use PostgreSQL instead of MySQL<br>to solve that problem?<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>> The bottleneck is how many developers know PostgreSQL AND care<br>> about Drupal using PostgreSQL, and willing to put in the effort to<br>> keep<br>> in tandem with MySQL so PostgreSQL does not lag behind.
<br><br></div>I recommand using pgAdmin III graphical client, which is the standard<br>graphical interface for PostgreSQL.<br><br>Also, log and analyse all SQL queries and plans.<br><br>Like in my HOWTO : PostgreSQL query optimisation =>
<br><a href="http://area51.phpbb.com/phpBB/viewtopic.php?f=3&t=29292" target="_blank">http://area51.phpbb.com/phpBB/viewtopic.php?f=3&t=29292</a><br></blockquote><div><br>How is this going to help with the main issue (lack of human resources
<br>on the PostgreSQL side)?<br><br>People who develop and deploy Drupal use mainly MySQL.<br><br>Should we give them more work to solve the problem of lack or<br>resource (or the pgSQL folk not contributing)?<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>It is pretty hard against MySQL. Sorry, this is the opinion of most<br>people designing databases. I may change my opinion when a better<br>transactional support is added with better SQL99 suppport.<br></blockquote><div>
<br>pgSQL is a better database than MySQL (at least MyISAM). No one is<br>saying otherwise. The issue is how the community is made up, not a technical <br>one.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Besides, I find Drupal sometimes slow on my testing installation. I will<br>try to debug SQL queries written for MySQL and will report them back.<br><br>Kind regards,<br><font color="#888888">Jean-Michel<br><br></font>
</blockquote></div><br><br clear="all"><br>-- <br>Khalid M. Baheyeldin<br><a href="http://2bits.com">2bits.com</a>, Inc.<br><a href="http://2bits.com">http://2bits.com</a><br>Drupal optimization, development, customization and consulting.