On Nov 11, 2007 5:17 PM, Karoly Negyesi <<a href="mailto:karoly@negyesi.net">karoly@negyesi.net</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;">
In my opinion, any patch should be committable to core once it works<br>on mysql and has a decent hope (use common sense) to work on<br>postgresql. Once it's committed those who care about postgresql, if<br>they so want to, can test and if there is a need, fix it.
<br><br>Prime example: <a href="http://drupal.org/node/146466" target="_blank">http://drupal.org/node/146466</a> this is the most<br>important patch we have currently as it makes Drupal search speedy and<br>nice. And it is more or less on hold just because noone is sure
<br>whether the postgresql update works or not.<br></blockquote><div><br>I know many will not like what I will say, but I have to say it.<br><br>A prime example of where MySQL works fine to solve an issue with a few lines is this issue
<a href="http://drupal.org/node/83738">http://drupal.org/node/83738</a>. All the huge changes and jumping through hoops is because of accomodating PostgreSQL <br><br>We introduced schema changes just because PostgreSQL cannot do case insensitive matching by default, while MySQL works fine. For the sake of 5% (or 1%) of the sites, we are increasing complexity.
<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>Regards,<br><font color="#888888"><br>Karoly Negyesi<br></font></blockquote>
</div><br><br clear="all"><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.