All-<br><br>This is ------NOT------- intended to open the database wars.<br><br>However, please take note of <a href="http://drupal.org/node/220064">http://drupal.org/node/220064</a>.<br><br>Drupaler <a href="http://drupal.org/user/194425" title="View user profile.">drupallfm</a> discovered a nasty (to us) little change from pgSQL 8.2 (which I test on) to 8.3.<br>
<br>It only seems to affect one core query, but could bite any developer who uses JOINS where data types are not identical.<br><br>From the Postgres website:<br><br>&quot;Upgrade Warning...in version 8.3 we have cleaned up some
of the data type conversions (&quot;casts&quot;). This refactoring may cause
problems for some users...&quot;<br clear="all"><br>What does it mean?&nbsp; It means that you cannot do a JOIN across different data types without casting your data.<br><br>In older versions of pgSQL (and in MySQL) the database handled the conversion for you.&nbsp; pgSQL 8.3 does not, and throws an error.<br>
<br>In D6, the only query that seems to be affected is <a href="http://api.drupal.org/api/function/block_box_get/6">http://api.drupal.org/api/function/block_box_get/6</a>.&nbsp; pgSQL used to turn the interger and varchar into text strings for comparison.&nbsp; It no longer does, so an explict CAST is necessary.<br>
<br>However, lets keep that in mind for D7 work on the db layer.<br><br>--<br>Ken Rickard<br>agentrickard <br>-- <br>--------------------------------------------------------------<br>DON&#39;T MISS EARTH&#39;S LARGEST GATHERING OF DRUPAL PROFESSIONALS!<br>
Drupalcon Boston 2008 · March 3-6, 2008<br>Learn more at <a href="http://boston2008.drupalcon.org">http://boston2008.drupalcon.org</a><br>Affordable sponsorship packages available<br>--------------------------------------------------------------