CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Post-installation Setup and Configuration (Moderator: Dave Greenberg) »
  • Views integration: SELECT command denied
Pages: [1]

Author Topic: Views integration: SELECT command denied  (Read 696 times)

pbeakley

  • I post occasionally
  • **
  • Posts: 30
  • Karma: 1
Views integration: SELECT command denied
May 25, 2010, 03:29:01 pm
Okay, I've gone through the Views2 integration documentation with a fine-tooth comb. I've added the list of prefixes to the end of my settings.php file. I've gone through every step of the Redspire recipe, including editing the eight different ['table']['base'] sets in civicrm/drupal/modules/views/civicrm.views.inc.

I can see all the CiviCRM data options in my Views UI, but when I build a query (usually via a Relationship), I get the SELECT command denied for user error.

It appears the query is not switching over to the settings under $db_url['civicrm'] = in my settings.php file. It's trying to access the correct database (aaee2010civicrm) but is using the default username (aaee2010drupal).

I've got my client set up on a GoDaddy shared hosting plan because it's cheap, but GoDaddy's shared hosting does not allow you to create multiple databases with the same username and password, nor can you create multiple credential sets for a single database. We'd have to upgrade to a virtual host or better, and that's not in their budget.

Now the only step in the Views2 integration document I totally did not understand was the reference to http://drupal.org/node/18429. Under the sentence "To query a different database, simply set it as active by referencing the key name.", and the code following, I have no idea where to put that. Is that something I have to hack Views itself to do? I am really hesitant to hack the core code.

I'm at a loss here, and feel stupid posting this because Views2 integration has been beaten to death so thoroughly on this forum. I'll take any lead anyone can give me. Thank you!

EDIT: I experimented with a couple ways to build an integrated query. First way was to create a "user" type query and attempt to build in a relationship to the user's CiviCRM contact information. That one gives me the "SELECT command denied" error. Then I tried building a query starting as a CiviCRM Contact type of View, and when I added the Drupal User ID relationship I got a "table not found" error. Think that's relevant?
« Last Edit: May 25, 2010, 04:03:33 pm by pbeakley »

pbeakley

  • I post occasionally
  • **
  • Posts: 30
  • Karma: 1
Re: Views integration: SELECT command denied
May 27, 2010, 02:13:29 pm
Well, it looks like this question is in the wrong forum. Very sorry! I'll repost it over in the Drupal forum.  :-[

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Post-installation Setup and Configuration (Moderator: Dave Greenberg) »
  • Views integration: SELECT command denied

This forum was archived on 2017-11-26.