Open Stack

On 05/17/2013 08:33 AM, Mark Washenberger wrote:
> I wonder if the best solution here is to change the uniqueness
> constraint in our tables (as has been mentioned in several other
> OpenStack-related database discussions) so that deleted images do not
> conflict with active images with the same uuid. As I recall, the best
> practice suggestion was to key the uniqueness constraint off the pair
> <uuid, deleted>. In this scheme, deleted is no longer a simple boolean,
> but rather either 0 (not deleted) or equal to the auto-increment row id
> (deleted).
> 
> Does that make sense?

In that case what happens when image is deleted again?