On Nov 28, 2007 5:48 AM, Chris Johnson <<a href="mailto:cxjohnson@gmail.com">cxjohnson@gmail.com</a>> wrote:<br><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;">
<br>If I were able to devote more time to just testing Drupal for the sake<br>of testing it and with no further purpose, I could and would use<br>Postgres more of the time. But even then -- if my goal were to test<br>the new menu code, I'd want to eliminate any other possible error
<br>causing sources, such as using Postgres.<br><br>So unless we actually push the issue of supporting multiple databases<br>as a community, the vast majority of developers will never make the<br>effort. And with each passing release spent in that mode, the harder
<br>it will become to reverse it. We will end up supporting only one<br>database, MySQL, de facto.<br></blockquote></div><br>Very good post Chris.<br><br>This is exactly the problem: those who use Drupal on PostgreSQL must
<br>be the ones who would resolve the SQL differences, test and debug patches,<br>...etc. <br><br>They are the ones that have a vested interest in it more than the rest<br>of us. All of us want a cross platform cross database CMS, but the testing
<br>work must be done by those who use PostgreSQL.<br><br>The rest of us have no time or resources to dedicate for something we <br>will not directly use.<br>-- <br>Khalid M. Baheyeldin<br><a href="http://2bits.com">2bits.com
</a><br><a href="http://2bits.com">http://2bits.com</a><br>Drupal optimization, development, customization and consulting.