<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">PostgreSQL is an SQL99 reference database. When you develop SQL code for
<br>PostgreSQL, you can silently run the code under any database.<br><br>On the converse, when designing SQL for a non-standard database,<br>you are more likely to loose time.<br></blockquote><div><br>That is all well and good from "it runs" (
i.e. unit testing, functionality is OK), <br>but when you try to optimize for large datasets or complex queries, 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><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">PostgreSQL is a real community of very pleasant people. We are not a<br>company, but a real team. Posting against PostgreSQL will certainly
<br>attract hundreds of PostgreSQL developers. Is that you silent dream?<font color="#888888"><br></font></blockquote></div><br>That is also good, but it is not the point.<br><br>We are not debating whether Pg or MySQL are better database, or who
<br>has a better community.<br><br>The bottleneck is how many developers know PostgreSQL AND care<br>about Drupal using PostgreSQL, and willing to put in the effort to keep<br>in tandem with MySQL so PostgreSQL does not lag behind.
<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.