|Anonymous | Login | Signup for a new account||2019-02-20 20:42 GMT|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000538||SiT!||setup/config||public||2009-03-02 18:48||2013-02-09 19:29|
|Target Version||3.90beta1||Fixed in Version||Current GIT|
|Summary||0000538: setup.php crashes if db user does not have ALTER privilege|
|Description||I just wanted to upgrade to 3.45. I did everything as described here: http://sitracker.org/wiki/ReleaseNotes [^]|
But I had a little problem. When I was running the DB upgrade script I got about 15 messages that the db user does not have ALTER privileges. My problem now is that I can not run the script again because setup.php thinks this version is already 3.45. But it is not (fully).
|Additional Information||So I have the following ideas:|
1) Check first if the user has the necessary privileges. Else give an error message before you do the upgrade.
2) If anything fails give the possibility to correct something and the let the administrator retry the failed commands.
3) Write in your documentation what privileges the db user exactly needs.
|Tags||No tags attached.|
You can correct this problem by dropping your database and running setup again,
or if this is an upgrade you can alter the 'system' table manually and change the version number to the version you are upgrading from and then run setup again.
You're right though, we should try better. We should probably ask for a root or admin MySQL user during setup to create the schema with.
Thanks, But I could solve the problem in a different way. I was looking at setup-schema.php (or whatever the exact name of the file was) and I copied the ALTER statements out and ran them with my root account.
It is working fine now. I just wanted to let you know and help you making the installation process more fool prove.
Yeah, thanks for logging it, it definitely is something we should look at for the next release.
Keep the good ideas coming... :-)
|Setup doesn't crash any more, but it doesn't offer the ability to install using different db credentials than the ones you intend to run as. We should look at that for a future release, but for now the workaround is to install using credential suitable for schema creation and then to manually edit your config file to use lesser credentials if required.|
|4e25f83 now checks the permissions and informs the user what is missing|
|documentation no updated as well.|
|2009-03-02 18:48||modir||New Issue|
|2009-03-04 15:35||ivan||Note Added: 0000688|
|2009-03-04 16:28||modir||Note Added: 0000694|
|2009-03-04 17:04||ivan||Note Added: 0000697|
|2009-03-04 17:04||ivan||Status||new => confirmed|
|2009-03-04 17:04||ivan||Target Version||=> 3.50|
|2009-07-25 14:06||ivan||Status||confirmed => assigned|
|2009-07-25 14:06||ivan||Assigned To||=> ivan|
|2009-07-25 14:46||ivan||Note Added: 0001397|
|2009-07-25 14:46||ivan||Target Version||3.50 => 3.60|
|2009-08-21 14:28||kieran||Target Version||3.60 => 4.0|
|2011-02-14 13:25||ivan||Target Version||4.0 => 3.90beta1|
|2011-06-16 09:40||ivan||Relationship added||has duplicate 0001603|
|2013-01-05 12:17||paulh||Assigned To||ivan => paulh|
|2013-01-06 12:24||paulh||Note Added: 0004640|
|2013-02-09 19:29||paulh||Note Added: 0004698|
|2013-02-09 19:29||paulh||Status||assigned => resolved|
|2013-02-09 19:29||paulh||Resolution||open => fixed|
|2013-02-09 19:29||paulh||Fixed in Version||=> Current GIT|
|Copyright © 2000 - 2019 MantisBT Team|