<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I’m just catching up on this thread, so this may have already
been answered. Regarding the case insensitivy, why can’t one use ILIKE during
the postGres search in the SQL statement to force case-insensitive?...again, as
I read more through this thread, this may have been answered.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> development-bounces@drupal.org
[mailto:development-bounces@drupal.org] <b>On Behalf Of </b>Khalid Baheyeldin<br>
<b>Sent:</b> Sunday, November 11, 2007 7:31 PM<br>
<b>To:</b> development@drupal.org<br>
<b>Subject:</b> Re: [development] Do not let postgresql hold back great patches<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>On Nov 11, 2007 5:17 PM, Karoly Negyesi <<a
href="mailto:karoly@negyesi.net">karoly@negyesi.net</a>> wrote:<o:p></o:p></p>
<div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<p class=MsoNormal>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.<o:p></o:p></p>
</blockquote>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><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. <o:p></o:p></p>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<p class=MsoNormal><br>
Regards,<br>
<span style='color:#888888'><br>
Karoly Negyesi</span><o:p></o:p></p>
</blockquote>
</div>
<p class=MsoNormal><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. <o:p></o:p></p>
</div>
</body>
</html>