2009/4/19 Chris Meller <[email protected]> > http://drupal.org/node/354139 >> >> http://www.semicomplete.com/blog/geekery/mysql-prepare-queries-not-cached.html >> > > We set this on connect for MySQL in system/schema/mysql/connection.php > (although I don't remember why, since MySQL shouldn't have this kind of > problem). We should probably add that for Postgres as well. > >
I think people tend to use it to take advantage of query caching in MySQL or something along those lines. > > Is the problem with COUNT(1), or AND (1)? I'm assuming the latter. > > Is it supposed to be AND (1=1)? I know several places we do that when we're > putting together WHERE clauses in pieces so the array containing pieces > always has at least one element... > It is a problem with AND (1), for sure. I am not very familiar with the code yet, I'll have to follow the logic a little bit and find out where this gets produced, but if it reminds anyone something relevant, please jump straight in... > > All of this is surprising. Neither problem seems to have anything to do > with ACL and would seem to have been an issue previously as well. Those are > the only issues you've run into with trunk on Postgres? Are you sure the > schema got created correctly? Have you tried an upgrade from 0.5 to > 0.6/trunk? > ahem, I'm not entirely sure this is error is all that stands in the way of full postgresql support, but it's certainly the last error message I get for the dashboard page when I log in. I have not tried the 0.5 at all, I initially tried the official 0.6 release and when that didn't work I checked out 3482. But the installation worked for 3482, tables were created and populated, and I was able to post something, even before I started looking at the code. But dashboard doesn't work, and while you're logged in, the non-admin pages don't work either. so, fixing the dashboard seems a good step. cheers, Michael --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
