DB Errors after "successful" upgrade to 4.5.2

[Rob Hills]

Hi Dave,

Sorry that didn't work out, could you try this patch instead, against the original version?

That's fine, I understand how difficult it is to debug an issue that you can't easily reproduce.  I'm delighted to report that your latest patch has resolved the issue for me.

Also did you try setting up the prefixes for the Civi tables in settings.php, as I described in my comment of 18th Nov? That shouldn't be necessary with this new patch, but is another way to get it working if you're not able to patch immediately. It's something you would need to do anyway if you wanted to use Civi Views integration at some point.

I hadn't done this before now, as I wanted to be able to prove that your patch fixed my primary issue.  Now that I've proven that, I will go and sort out the configuration issue.

Many thanks,

[hwcb]

Thanks, Dave!

After upgrading from 4.4 to 4.5, I had the same problem Rob described. I applied your patch, and it fixed it.

[nickholden]

Thanks, Dave. I didn't realise the module was attempting to access both the Drupal and Civi databases in a single query. Given that the architecture allows the two systems to have dbs on completely different database servers that probably isn't a future proof approach. Your patch certainly solved the problem for me. No more error messages on log in. Nice work.

Will the fix make it into the next 4.5.x release, or will it wait for 4.6?

[davej]

I've created a pull request against the 7.x-4.4 civicrm-drupal branch, in the hope that this fix can go into 4.4.x LTS as well as 4.5 .

See https://issues.civicrm.org/jira/browse/CRM-15644?focusedCommentId=67901&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-67901