Claims don't work with mysql

[Flavio Percoco]

When using mysql, claims doesn't seem to work. It can be verified by running the claims example in marconi client. It works perfectly when using sqlite but not with mysql

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/78672
Committed: https://git.openstack.org/cgit/openstack/marconi/commit/?id=477bc46bfe1d7e1c056a4bb4aaa72d452315c160
Submitter: Jenkins
Branch: master

commit 477bc46bfe1d7e1c056a4bb4aaa72d452315c160
Author: Flavio Percoco <email address hidden>
Date: Thu Mar 6 18:08:22 2014 +0100

    Set time_zone to UTC on MySQL

    MySQL uses UTC for all date fields but other operations like `now()` use
    the timezone of the server. This patch changes the timezone of the
    connection to UTC when the connection is first established.

    There's space for improvement here. For instance, we could try to avoid
    doing this for every new connection and let the operator configure it on
    the server side. We could also use `CONVERT_TZ` on every query using
    `now()`.

    Change-Id: I2e8415dbb9a6ce19d3a66f3226756094b3e0f6a4
    Partial-bug: #1288820

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/78673
Committed: https://git.openstack.org/cgit/openstack/marconi/commit/?id=364945f9902302e23cb6164377f5a310a82a2839
Submitter: Jenkins
Branch: master

commit 364945f9902302e23cb6164377f5a310a82a2839
Author: Flavio Percoco <email address hidden>
Date: Thu Mar 6 18:10:54 2014 +0100

    Reuse the transaction before getting messages

    The message get helper for claims used its own connection and ran
    outside the transaction where the 'claiming' happened. This caused the
    get to fail at retrieving the messages because the query was being
    executed 'before' the transaction.

    This patch fixes the aforementioned issue and also ensures that records
    ids are 'int' before calling `message_encode`.

    Change-Id: I076ffc171adf02fdb15160b6c7b29646ee3fb280
    Closes-bug: #1288820