My understanding of best practices is that all tables should have a primary key to make database queries run faster.
We also need this for our database replication solution.
| Comment | File | Size | Author |
|---|---|---|---|
| #17 | password_policy-7.x-1.x-add_a_primary_key-2715281-17.patch | 751 bytes | aohrvetpv |
| #10 | password_policy_force_change_2715281-10.patch | 755 bytes | diego_mow |
Comments
Comment #2
rocket777 commentedComment #3
rocket777 commentedThis patch makes the uid column a primary key.
This patch created similar to this issue https://www.drupal.org/node/2701489
Credit to jrglasgow.
Comment #4
rocket777 commentedComment #6
rocket777 commentedSame patch, applies to v1.12
Comment #7
rocket777 commentedComment #8
harivenuvHi roket777,
Thanks for the patch. You have little bit careful about coding stands. I have created a patch to correct the coding standard.
Comment #10
diego_mow commentedChanging the hook_update number from patch password_policy_force_change_2715281-7.patch.
Comment #11
diego_mow commentedComment #13
aks22 commentedComment #15
aks22 commentedHi, Patch-10 i have retested with 7.x-1.x password_policy_force_change_2715281-10.patch is working fine and also passed test.
So you may consider the patch-10.
Thanks.
Comment #16
aks22 commentedComment #17
aohrvetpv commentedChanged the update function comment slightly for consistency with other update functions. (They refer to tables using "{table_name}".)
Comment #20
aohrvetpv commentedI believe this is an unrelated problem with a test method, not a problem with the patch. Will investigate the failure.
Comment #22
aohrvetpv commented