Support from Acquia helps fund testing for Drupal Acquia logo

Comments

nedjo’s picture

Status: Needs review » Reviewed & tested by the community

I reviewed the patch. It is thorough and covers the various places where changes are needed:

* In db queries, both old-style like db_query() and new-style like db_select().
* In the table sharing example in default.settings.php. Existing sites upgrading from previous versions will retain incorrect sample code in their legacy settings.php files, but rewriting those in the update doesn't seem doable, given file permissions issues.
* In code comments that name the table.
* In the session table schema.
* In an update function.

nedjo’s picture

I guess my only question would be: does it make sense to put each of these table name changes in a separate update function, or should they be done in groups? In system_update_7012() we renamed three tables related to blocks. (Come to think of it, I'm not sure why that update is in system.install and not block.install.)

Should we put all changes to tables in system.install's schema in the same update? If so, should this patch include all remaining tables in system_schema() that need renaming?

boombatower’s picture

If we choose to do that...I think we should add each of the table renames to the hook as we commit them... I would prefer not to make a mega patch...and since we aren't worried about HEAD-HEAD upgrades if we keep adding to the same hook should be ok.

@nedjo: Thanks for the thorough review.

recidive’s picture

Status: Reviewed & tested by the community » Needs work

As explained in #330983-15: Rename user module tables to singular, upgrade path will not work.

boombatower’s picture

Status: Needs work » Postponed

Will add to update_prepare_d7_bootstrap_rename() once users patch gets in.

boombatower’s picture

Status: Postponed » Needs review

other fixed.

Status: Needs review » Needs work

The last submitted patch failed testing.

boombatower’s picture

Status: Needs work » Needs review
FileSize
8.63 KB

Since user table rename patch got in this needs re-roll.

The session tables have same issue that user tables do and as such need to be hard-coded into update.php.

EDIT: The patch has a spacing issue in default.settings.php

'session'  => 'shared_',

Needs additional spacing.

Dries’s picture

I obviously support this patch but it needs a little bit more work per the discussion in this issue. Keep workin' it! :)

Dries’s picture

Status: Needs review » Needs work
boombatower’s picture

Status: Needs work » Reviewed & tested by the community

#2 and #4 are both dealt with since #330983: Rename user module tables to singular made it in and this patch uses that format.

Since was originally reviewed in #1 and only two issues fixed marking as RTBC.

NOTE: Tests passed, but results were ignored since this issue was marked as needs work. http://testing.drupal.org/pifr/file/1/4462

Josh Waihi’s picture

no key-word conflicts with session in postgresql. I'm happy.

David_Rothstein’s picture

Note that there is a problem with the way the {sessions} table is being renamed in update.php, and this is being discussed at #330983: Rename user module tables to singular. However, the problem is the same with the {users} table, so this doesn't cause any additional problems that weren't already there, and it could probably be fixed all at once at the other issue. So this is probably ready to go in..

Status: Reviewed & tested by the community » Needs work

The last submitted patch failed testing.

jacob.embree’s picture

Version: 7.x-dev » 9.x-dev
Assigned: boombatower » Unassigned
Issue summary: View changes
Parent issue: » #140860: Consistent table names and database handling of table names

Bumping version.

catch’s picture

Status: Needs work » Postponed (maintainer needs more info)
xjm’s picture

Version: 9.x-dev » 8.8.x-dev
Status: Postponed (maintainer needs more info) » Closed (won't fix)

I'd sat that this is a wontfix. I agree with #16.