Description: ------------ Bug fix 561, specifically the fix to DB_NestedSet->_getSelectFields(), adding a call to _quote() around aliased field names, causes problems, at least in Postgres. _quote() adds single quotes (') which work for mysql (although it should be back ticks (`)). But it generates an error in pgsql queries. See http://marc.theaimsgroup.com/?t=108085269100002&r=1&w=2 for pgsql results. I think you need to use quoteIdentifier() instead of _quote().

Actually, there's another problem with fix 561. Instead of _quote(), _values2InsertQuery() was edited to place back ticks around insert field values, which also breaks pgsql. I think both cases should use quoteIdentifier().

Hello Andy, this is really dumb. I spent some hours on the quoting issue and found out that different RDBM's have totally complementary implementations for the quoting things. E.g. mySQL only accepts backticks for field names used inside an insert/update query. But I thought I had figured it out - I was wrong :\ Unfortunately MDB doesn't support quoteIdentifier yet. Which means that MDB will not work with reserved words used for column names till it supports this type of quoting. Could you please fetch NestedSet.php and Nested/set/DB.php,MDB.php to see if the problem is fixed for you now? I'll add pgsql to my testsuite setup now - promise! -- Daniel Khan

O.K. here's a snapshot http://devel.webcluster.at/~daniel/DB_NestedSet/DB_NestedSet-1.3.4.tgz As soon as I know that it works for you now I'll do a new release.

Hi Daniel, Eyeballed the changes and they appear OK. And testing on MySQL I found no problems. I forwarded this on to other Seagull developers for testing on pgsql (I don't have it either) and will let you know what they say. Andy

Thanks a lot. Yes mySQL should work for sure as I am using it in my testsuites.

Hi Daniel, Looks like your fixes at http://devel.webcluster.at/~daniel/DB_NestedSet/DB_NestedSet-1.3.4.tgz did the trick. See http://marc.theaimsgroup.com/?l=seagull-general&m=108103309217240&w=2. Andy

Thank you for your bug report. This issue has already been fixed in the latest released version of the package, which you can download at http://pear.php.net/packages.php