yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1182054] Re: wrong unique constraint names

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>
Date: Wed, 17 Jul 2013 12:13:07 -0000
Reply-to: Bug 1182054 <1182054@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => havana-2

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1182054

Title:
  wrong unique constraint names

Status in OpenStack Compute (Nova):
  Fix Released
Status in Oslo - a Library of Common OpenStack Code:
  Fix Released

Bug description:
  There is unique constraint name convention: "uniq_c1_x_c2_x_c3" means
  that columns c1, c2, c3 are in UniqueConstraint.

  But there are some constraints that don't much this convention, such as
  - key_pairs_uniq_name_and_user_id,
  - virtual_interfaces_address_key,
  - instance_info_caches_instance_uuid_key

  It works fine with sqlite but if we will use mysql or postgresql in
  case of integrity error we can't get column names from error message.

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