| 2013-05-20 13:07:06 |
Viktor Serhieiev |
bug |
|
|
added bug |
| 2013-05-20 13:07:14 |
Viktor Serhieiev |
nova: assignee |
|
Victor Sergeyev (vsergeyev) |
|
| 2013-05-20 13:07:23 |
Viktor Serhieiev |
nova: status |
New |
In Progress |
|
| 2013-05-20 13:10:58 |
Boris Pavlovic |
nova: importance |
Undecided |
High |
|
| 2013-05-20 13:22:25 |
Viktor Serhieiev |
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:
- instance_uuid,
- uuid,
- key_pairs_uniq_name_and_user_id,
- address |
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:
- instance_uuid,
- uuid,
- key_pairs_uniq_name_and_user_id,
- address.
It works fine with sqlite but if we will use mysql or postgresql in case of IntegrityError
we can't get column names from error message. |
|
| 2013-05-20 13:22:49 |
Viktor Serhieiev |
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:
- instance_uuid,
- uuid,
- key_pairs_uniq_name_and_user_id,
- address.
It works fine with sqlite but if we will use mysql or postgresql in case of IntegrityError
we can't get column names from error message. |
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:
- instance_uuid,
- uuid,
- key_pairs_uniq_name_and_user_id,
- address.
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. |
|
| 2013-05-22 12:50:20 |
Viktor Serhieiev |
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:
- instance_uuid,
- uuid,
- key_pairs_uniq_name_and_user_id,
- address.
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. |
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. |
|
| 2013-05-28 10:14:26 |
Mark McLoughlin |
bug task added |
|
oslo |
|
| 2013-05-28 10:14:33 |
Mark McLoughlin |
oslo: status |
New |
In Progress |
|
| 2013-05-28 10:14:37 |
Mark McLoughlin |
oslo: importance |
Undecided |
Medium |
|
| 2013-05-28 10:14:50 |
Mark McLoughlin |
oslo: assignee |
|
Victor Sergeyev (vsergeyev) |
|
| 2013-05-28 10:14:56 |
Mark McLoughlin |
oslo: importance |
Medium |
High |
|
| 2013-05-28 13:50:50 |
OpenStack Infra |
oslo: status |
In Progress |
Fix Committed |
|
| 2013-05-30 09:47:53 |
Thierry Carrez |
oslo: status |
Fix Committed |
Fix Released |
|
| 2013-05-30 09:47:53 |
Thierry Carrez |
oslo: milestone |
|
havana-1 |
|
| 2013-06-07 19:53:12 |
OpenStack Infra |
nova: status |
In Progress |
Fix Committed |
|
| 2013-07-17 12:13:07 |
Thierry Carrez |
nova: status |
Fix Committed |
Fix Released |
|
| 2013-07-17 12:13:07 |
Thierry Carrez |
nova: milestone |
|
havana-2 |
|
| 2013-10-17 09:06:31 |
Thierry Carrez |
oslo: milestone |
havana-1 |
2013.2 |
|
| 2013-10-17 11:46:15 |
Thierry Carrez |
nova: milestone |
havana-2 |
2013.2 |
|
