The recommended naming of tables for sub-projects is documented. The
risk of conflicting names is low enough that it is not worth the effort
to implement checks across sub-projects. Marking as Won't-Fix. This can
be revisited if it becomes a problem.
** Changed in: neutron
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1347361
Title:
There should be a naming convention for neutron DB tables
Status in neutron:
Won't Fix
Bug description:
Now that the database is healed and all tables are present, the names
of tables are haphazard and there is no convention for avoiding naming
conflicts or having sensible grouping.
A naming convention may look something like:
<vendor>_<plugin|service>_<feature|purpose>
Existing tables should be renamed to follow the convention.
A README file explaining the convention should be created in the
directory with the models.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1347361/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
