The standard Drupal convention is to use singular names for all tables (e.g., {node}, {role} - there are exceptions in core, but each with specific reasons). We violate this, and should fix it.
Not pressing, though.
The standard Drupal convention is to use singular names for all tables (e.g., {node}, {role} - there are exceptions in core, but each with specific reasons). We violate this, and should fix it.
Not pressing, though.
Comments
Comment #1
marvil07 commentedOk as official docs, but this is going to be a medium patch :-p
Comment #2
cweagansTaking this.
Comment #3
cweagansOkay, just kidding. Not tonight.
Comment #4
marvil07 commentedmoving to major, since it's a db change, and I think it would be great to avoid db changes after the 2.0-RC1
Comment #5
marvil07 commentednot confirmed for sprint 4, but tagging to avoid forgetting about it
Comment #6
sdboyer commentedyeah, we've got other more critical stuff for sprint 4, untagging.
Comment #7
marvil07 commentedI am postponing this until #879858: Unify entity C(R)UD and #879600: Meta: introduce an activity stream separate from commit logs gets in, to avoid unnecessary patches conflict.
Comment #8
sdboyer commentedYeah, no.
Comment #9
marvil07 commentedtagging
Comment #10
marvil07 commentedSince #879600: Meta: introduce an activity stream separate from commit logs is not a release blocker, and we are kind of late for a schema change like that, I move this to the next major version of versioncontrol.