Failing to grant 'Drop' privileges to db user during install locks install process without manual db cleanup

Created on 6 January 2011, almost 14 years ago
Updated 11 April 2024, 9 months ago
  1. Attempted to connect my new Drupal 7 installation to a MySQL DB as a user without DROP permissions.
  2. Received error message about DROP permissions and gave the user correct permissions.
  3. Retried and received the following as the 'drupal_install_test'-DB was not created because it couldn't be previously dropped.
  4. Failed to CREATE a test table on your database server with the command CREATE TABLE {drupal_install_test} (id int NULL). The server reports the following message: SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'drupal_install_test' already exists.
    Are you sure the configured username has the necessary permissions to create tables in the database?

    That last message would send you in the wrong direction if the server isn't as kind as this one, giving the error quite clearly.

    Perhaps the process that tests for CREATE & DROP permissions should check if the table already exists before attempting to create it again?

πŸ› Bug report
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component
DatabaseΒ  β†’

Last updated 3 days ago

  • Maintained by
  • πŸ‡³πŸ‡±Netherlands @daffie
Created by

πŸ‡ΈπŸ‡ͺSweden lawik

Live updates comments and jobs are added and updated live.
  • Needs backport to D7

    After being applied to the 8.x branch, it should be considered for backport to the 7.x branch. Note: This tag should generally remain even after the backport has been written, approved, and committed.

  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡³πŸ‡ΏNew Zealand quietone

    Checking in on this issue which hasn't has any work for 8 years to find out if it is still relevant.

    Is this still relevant to Drupal 10?

    Since we need more information to move forward with this issue, I am setting the status to Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024