Property DB operations are not consistent with the rest of the API

[Flavio Percoco]

Property related functions are not consistent with the rest of the API.

image_property_create returns a models.ImageProperty instance instead of a dictionary as the image function does.

image_property_delete receives an models.ImageProperty instance instead of a reference name.

It is important to:

1) Keep API's consistency
2) Avoid making the DB API back-end dependent.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/36218

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/36218
Committed: http://github.com/openstack/glance/commit/ba17ee92f4110309da305fc2a80941abc997871e
Submitter: Jenkins
Branch: master

commit ba17ee92f4110309da305fc2a80941abc997871e
Author: Flaper Fesp <email address hidden>
Date: Tue Jul 9 15:10:58 2013 +0200

    Make db properties functions consistent with the DB API

    Currently property related functions are not consistent with the
    database API. As for the create operation, the API returns an
    ImageProperty model instead of a dictionary and in the case of the
    delete operation, the function expects a property instance instead of a
    reference name.

    This patch makes both calls consistent by returning a dictionary when a
    property is created and receiving a property name instead of its
    instance when a property needs to be deleted.

    Fixes bug: #1199364
    Implements blueprint registry-db-driver

    Change-Id: Ibc7067cf712942610c7507f22f8895c2d531172a

[Zack Mu (zackmys8)]

We are able to perform a wide range of adhesive strength tests, such as tensile, shear, and peel tests, in addition to other critical evaluations like impact resistance, odour analysis, and ageing behaviour. https://www.uvcureadhesive.com/