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 »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Upgrade from 4.29 to 4.3 (CiviCRM 4.3.0 requires MySQL trigger privileges)
Pages: 1 [2]

Author Topic: Upgrade from 4.29 to 4.3 (CiviCRM 4.3.0 requires MySQL trigger privileges)  (Read 9946 times)

Interpolat

  • I post frequently
  • ***
  • Posts: 140
  • Karma: -1
    • Interpolat Solutions, LLC.
  • CiviCRM version: 4.4+
  • CMS version: Wordpress
  • MySQL version: 5.5+
  • PHP version: 5.4+
Re: Upgrade from 4.29 to 4.3 (CiviCRM 4.3.0 requires MySQL trigger privileges)
May 17, 2013, 03:51:34 pm
Thanks for your response nextwave.  However, I am still in a cloud and am not sure what to tell the hosting company.  There is no access to WHM on this account, so whatever tweeks need to be done will be done by the hosting company.  And to do this, they want to know specifically, what triggers are required by CiviCRM?
Interpolat Solutions, LLC
Connecting the dots for you!
http://www.interpolat.com

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Upgrade from 4.29 to 4.3 (CiviCRM 4.3.0 requires MySQL trigger privileges)
May 17, 2013, 04:33:21 pm

Note that we drop and recreate triggers and views during all upgrades. Sending the hosting company a bunch of sql to execute is a process best avoided (IMO)

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

The Next Wave

  • I post occasionally
  • **
  • Posts: 111
  • Karma: -9
  • I'm just here to change the world.
  • CiviCRM version: 4.4.4
  • CMS version: Wordpress 3.8.1
  • MySQL version: 5.1.72-cll
  • PHP version: 5.4.25
Re: Upgrade from 4.29 to 4.3 (CiviCRM 4.3.0 requires MySQL trigger privileges)
May 17, 2013, 05:40:29 pm
@JMdezigns-
they have to access whm-
and you tell them to do this:
We go into cpanels whm-
to PHPmyAdmin
select> users
pick the database user- for Civi- and edit privileges
under admin- make it "super"

That's it.

Interpolat

  • I post frequently
  • ***
  • Posts: 140
  • Karma: -1
    • Interpolat Solutions, LLC.
  • CiviCRM version: 4.4+
  • CMS version: Wordpress
  • MySQL version: 5.5+
  • PHP version: 5.4+
Re: Upgrade from 4.29 to 4.3 (CiviCRM 4.3.0 requires MySQL trigger privileges)
May 17, 2013, 09:34:49 pm
I think if my understanding of your suggestion is correct, this would give me trigger privileges, which the company does not want to do.  Instead, they want to run the install script themselves.

Quote from: The Next Wave on May 17, 2013, 05:40:29 pm
@JMdezigns-
they have to access whm-
and you tell them to do this:
We go into cpanels whm-
to PHPmyAdmin
select> users
pick the database user- for Civi- and edit privileges
under admin- make it "super"

That's it.
Interpolat Solutions, LLC
Connecting the dots for you!
http://www.interpolat.com

HanV

  • I post occasionally
  • **
  • Posts: 35
  • Karma: 0
Re: Upgrade from 4.29 to 4.3 (CiviCRM 4.3.0 requires MySQL trigger privileges)
May 30, 2013, 05:39:47 am
Addition to my first post (creating this topic)
I have seen that i am using
    mysqlnd 5.0.10 (mysql native driver)
   phpinfo: Client API library version mysqlnd 5.0.10 - 20111026 
in php.ini php_pdo_mysql extension is enabled

Is this the good mysqlnd for mysql 5.5.24?
HanV

HanV

  • I post occasionally
  • **
  • Posts: 35
  • Karma: 0
Re: Upgrade from 4.29 to 4.3 (CiviCRM 4.3.0 requires MySQL trigger privileges)
June 19, 2013, 08:13:08 am
I have phpmyadmin 3.5.5, when I select the civicrm user I see the global rights (none), and on the database civicrm page the rights on civicrm (all except GRANT under ADMIN) en rights on the tables in civicrm (empty). Adding GRANT makes no difference (I have tried that before and now again).

I have replaced in civcrm-settings the civicrm-user with the root-user and it works. The upgrade seems to do all the steps in the upgrade without problems. And the application seems OK.
HanV

ernesto.sun

  • I’m new here
  • *
  • Posts: 3
  • Karma: 2
  • CiviCRM version: 4.2.7
  • CMS version: Drupal 7
  • MySQL version: 5.xx
  • PHP version: 5.xx
Re: Upgrade from 4.29 to 4.3 (CiviCRM 4.3.0 requires MySQL trigger privileges)
July 26, 2013, 03:29:53 am
Hey friends!

I really want to mention that I am very sad that CiviCRM is not learning it's lessions and keeping with triggers, views a.s.o.

As DB-engineer I can definitely say that triggers are NOT needed at all. No reference-constraints and also no views. It is nothing else than bad practice and creation of dependency.

Please do not wonder if CiviCRM-usage will go down soon. RESTful and lightweight-solutions have green light.

The sentence written by admins: "CiviCRM is a heavy-weight-system" is not legitimated technically at all. Sorry, what shall be heavy-weight at a CRM??

The only heavy-weight-part might be the mailing-servers who have to handle thousands of recipients. Everything else is just a DB-web-app.

Sorry for the world, sorry for CiviCRM that there seems not to be the willingness to look into a simple future.

Keep it small and simple as long as you want the planet to be happy with CiviCRM. I expect there are not only positive-minded people working in the team any more. As usual, when something becomes too useful for the public, some other people jump into the team and care for the 'right way' of development.

Sorry for us all!

All (=) Love, Ernesto ~:)

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Upgrade from 4.29 to 4.3 (CiviCRM 4.3.0 requires MySQL trigger privileges)
July 26, 2013, 05:53:07 am

can u elaborate a bit as to why triggers, views and foreign key constraints are bad. Links to valid sources would be good and beneficial

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

ernesto.sun

  • I’m new here
  • *
  • Posts: 3
  • Karma: 2
  • CiviCRM version: 4.2.7
  • CMS version: Drupal 7
  • MySQL version: 5.xx
  • PHP version: 5.xx
Re: Upgrade from 4.29 to 4.3 (CiviCRM 4.3.0 requires MySQL trigger privileges)
July 26, 2013, 06:14:51 am
Hey Donald!

First of all I want to say how thankful I am. I use CiviCRM for two+ organisations. One is big: Global Ecovillage Network and I suggest definitely donating to you, great developers!!

Maybe the reason why I like CiviCRM so much is also the reason why I am soooo sad that you use triggers, constraints and such..

Well, yes. I can find link telling what I want to tell you.

But get my point: There are many 'complex' systems out there and some proofed to keep simple and clean. Some are really easy to migrate and to switch between domains and so. E.g. Drupal 7

What do those systems do: They use standard-features and nothing else. That further helps them to be independent of the SQL-server and so.

Please think about that: Can you imagine ONE thing you really NEED to have something else than usual Tables, Keys and Indexes?!?!

I am developing for industries as well. I never saw one reason to use any other MySQL-feature than the mentioned ones.

There is simply NO use-case where you really NEED triggers or constraints. They are kind of 'luxury' which leads in a real hell.

---------------------------------
I am willing to jump into a development-branch of CiviCRM which removes all dependencies which are not common on cheap hosted servers.
---------------------------------

I just updated from Civi 4.2.7 to Civi 4.3.5. Man, that was bad. The updating-process just skipped with an error when it was not able to fullfill some reference-constraint. I had to remove/change the update-SQL inside the scripts in Civi/Updater/...  I was working locally (Had to fake the domain also, another dependency) and still, my root-MySQL-acount wasn't enough.

Or, look at the directory-entries in the file: sites\default\files\civicrm\ConfigAndLog\Config.IDS.ini   Why?? Why another place else than the setting-file.

Such things cost hundreds of hours at the customer-side. Why all this? I see no reason technically. Sorry. It is just bad design.

----

CiviCRM shall go REST and HTML5. Do you like this vision? If you need me, I am willing to contribute!

All (=) Love, Ernesto ~:)
 
PS: I am not allowed to post external links into the forum yet it seems.

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Upgrade from 4.29 to 4.3 (CiviCRM 4.3.0 requires MySQL trigger privileges)
July 26, 2013, 08:07:13 am

I think we'll agree to disagree here and move on

Civi has been using foreign key constraints since the first release

yes, we can write a fair bit of code to avoid using triggers / views etc, but we also wanted to build on the feature set of databases (and that is common across all DB's not just mysql).

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

ernesto.sun

  • I’m new here
  • *
  • Posts: 3
  • Karma: 2
  • CiviCRM version: 4.2.7
  • CMS version: Drupal 7
  • MySQL version: 5.xx
  • PHP version: 5.xx
Re: Upgrade from 4.29 to 4.3 (CiviCRM 4.3.0 requires MySQL trigger privileges)
July 26, 2013, 11:32:53 am
Hey Donald!

I totally understand to keep with the way it has been. Even if there is nothing steady, but the change.

Well, new Open Source CRM are created at the moment using new approaches. It is sad for CiviCRM

* that it will only be used then if no migration-path is available to the customer
* that the great knowledge and experience you gathered will not sustain directly

Well, whenever you decide to open yourself for a mayor reengineering let me know. I would love this approach.

Thanks for being so open. Knowing that, I also know that I have to:

* ensure MySQL-privileges for 'all future'
* be aware that a RESTful CiviCRM is a question of many years

Thanks!! And thumbs up!!

All (=) Love, Ernesto ~:)



The Next Wave

  • I post occasionally
  • **
  • Posts: 111
  • Karma: -9
  • I'm just here to change the world.
  • CiviCRM version: 4.4.4
  • CMS version: Wordpress 3.8.1
  • MySQL version: 5.1.72-cll
  • PHP version: 5.4.25
Re: Upgrade from 4.29 to 4.3 (CiviCRM 4.3.0 requires MySQL trigger privileges)
November 11, 2013, 04:28:48 pm
Once again on a update we have mysteries.
One install kept failing with trigger privilege messages- the other two were fine.
Only thing we've found - and we're mystified on how it happened- is some of the files in the db had switched to ISAM from INNODB.
After manually correcting them all- we'll see what happens- but, this is really tedious.
Why can't CiviCRM update as gracefully as wordpress?
C'mon people.
I find it interesting that this is the only software we've ever worked with that requires trigger privileges and the only one that seems to freak out if it uses ISAM- I don't understand either of these- but, I wonder why Lobo blows off Ernesto with his suggestions to not require Trigger privileges?
The frustration of people on this forum is real- for Civi to take off- you have to find ways to eliminate these problems.

The Next Wave

  • I post occasionally
  • **
  • Posts: 111
  • Karma: -9
  • I'm just here to change the world.
  • CiviCRM version: 4.4.4
  • CMS version: Wordpress 3.8.1
  • MySQL version: 5.1.72-cll
  • PHP version: 5.4.25
Re: Upgrade from 4.29 to 4.3 (CiviCRM 4.3.0 requires MySQL trigger privileges)
November 13, 2013, 07:11:13 am
CPanel has changed the way you access trigger privileges- and made this really complex.
I have no clue what to do about this- these were the instructions from my Hosting center on a possible solution to this issue- and it sure looks overly complex:
Quote
For the phpMyAdmin issue, I'd recommend creating a new cPanel account and installing a non-cPanel driven copy of phpMyAdmin there.  cPanel made a *lot* of changes to their phpMyAdmin installation in the last release, and it appears they've removed all of the functions you use regularly.  We can edit their config to put them back, but it will get overwritten every night when cPanel updates.  If you create a "mysqladmin.nextwavehosting.net" account, you can install your own, non-cPanel copy of phpMyAdmin directly in public_html.  I'd recommend doing this, and making public_html password-protected so there are 2 levels of authentication.  The root MySQL password is in /root/.my.cnf on the server for the configuration of the new PMA instance, but this appears to be the best way for you to have a full, uninhibited copy of PMA to do what you require.
Since CPanel is running about a third of LAMP servers- I think some very detailed instructions on how exactly trigger privileges are set in this environment are MANDATORY- so CiviCRM can continue to be taken seriously.
I am more than willing to set up an account on my server for one of the Civi people who insist on including trigger privileges as part of the setup for Civi- to try to install and run the software using Cpanel as a setup tool- so they can document it for us n00bs who are trying to change the world- instead of becoming programmers.

andros

  • I’m new here
  • *
  • Posts: 13
  • Karma: 0
  • CiviCRM version: 4.2.1
  • CMS version: Drupal 7.12
  • MySQL version: 5.1.62-MariaDB
  • PHP version: 5.3.15
Re: Upgrade from 4.29 to 4.3 (CiviCRM 4.3.0 requires MySQL trigger privileges)
February 08, 2014, 08:27:58 am
This is maybe helpful for some who has the "requires MySQL trigger privileges" problem.

http://issues.civicrm.org/jira/browse/CRM-12315

I have come to this error my self after enabling binary logging in mysqld. If you use binary logging you need SUPER privileges too.

Pages: 1 [2]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Upgrade from 4.29 to 4.3 (CiviCRM 4.3.0 requires MySQL trigger privileges)

This forum was archived on 2017-11-26.