yahoo-eng-team team mailing list archive

[Mark McClain <1292397@xxxxxxxxxxxxxxxxxx>]

I believe this is a not bug, but a difference in the implementation of
the databases.  Unless there is a decided performance reason, I do not
see the need to add code to make the databases look the same.  Postgres
creates an index on the primary key of the related table.

** Changed in: neutron
       Status: In Progress => 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/1292397

Title:
  Difference in index creation for foreign key in MySQL and Postgres

Status in OpenStack Neutron (virtual network service):
  Won't Fix

Bug description:
  In some migration such as  39cf3f799352_fwaas_havana_2_model,
  569e98a8132b_metering, 1064e98b7917_nec_pf_port_del.
  ForeignKeyConstraint is created with name, but in models this name
  isn't mentioned. MySQL creates index when it creates
  ForeignKeyConstraint. So in database for MySQL there are special
  indexes, but there are no such indexes in database for PostgreSQL
  http://paste.openstack.org/show/76906/. This cause difference between
  models and migrations and between database content for MySQL and
  PostgreSQL. If ForeignKey is created without name there is no such
  problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1292397/+subscriptions