#195416: Table prefixes should be per database connection has been stalled for month, because PIFR uselessly tries to enforce an empty prefix (which is already the default), when installing Drupal.

Let's get rid of this.

CommentFileSizeAuthor
#1 839996-stop-enforcing-an-already-empty-default.patch760 bytesDamien Tournoud
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Damien Tournoud’s picture

Damien Tournoud CreditAttribution: Damien Tournoud commented
Status: Active » Needs review
FileSize
839996-stop-enforcing-an-already-empty-default.patch760 bytes

Here, simple patch.

Damien Tournoud’s picture

Damien Tournoud CreditAttribution: Damien Tournoud commented

Once this is in and we have deployed it, we can at least clean up the database settings page of Drupal 7 and rename db_prefix to prefix :)

boombatower’s picture

boombatower CreditAttribution: boombatower commented
Assigned: Unassigned » boombatower
Status: Needs review » Fixed

Hmm.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.