delta/openstack/taskflow.git/taskflow/persistence/backends/sqlalchemy/tables.py, branch master opendev.org: openstack/taskflow.git Use custom JSONType columns 2021-07-13T09:44:06+00:00 Pavlo Shchelokovskyy shchelokovskyy@gmail.com 2021-07-13T09:06:41+00:00 3e1f150926029b6a553cbef959f370e39ce6bb5a the JSONType from sqlalchemy_utils is quite brittle as it only does primitive json.dumps on values. This leads to various sorts of StorageFailure exceptions in taskflow when, for example, an unserializable exception bubbles up to the 'failure' field of AtomDetails. This patch sublclasses the JSONType from sqlalchemy_utils and overrides two of its methods that do (de)serialization to work via oslo.serialization functions. They deal with such occurencies much better, for example, by providing 'str' as a fallback default. Change-Id: I3b9e9498b155199a4e707006a0cf22cda0567c06 Related-Bug: #1935957 
the JSONType from sqlalchemy_utils is quite brittle as it only does
primitive json.dumps on values. This leads to various sorts of
StorageFailure exceptions in taskflow when, for example, an unserializable
exception bubbles up to the 'failure' field of AtomDetails.

This patch sublclasses the JSONType from sqlalchemy_utils and overrides
two of its methods that do (de)serialization to work via
oslo.serialization functions. They deal with such occurencies much
better, for example, by providing 'str' as a fallback default.

Change-Id: I3b9e9498b155199a4e707006a0cf22cda0567c06
Related-Bug: #1935957
Use the sqlalchemy-utils json type instead of our own 2015-09-10T00:54:11+00:00 Joshua Harlow harlowja@gmail.com 2015-06-04T04:55:15+00:00 598e09fb062daed36fd4f10943ce9b4381843c9e Change-Id: Ie01ea85e74f1daed6bfa5158c0faa476d06873ba 
Change-Id: Ie01ea85e74f1daed6bfa5158c0faa476d06873ba
Retain atom 'revert' result (or failure) 2015-07-11T01:12:48+00:00 Joshua Harlow harlowja@yahoo-inc.com 2015-06-17T18:28:57+00:00 a3fe3eb698e7bfa20b0b7fddd91c37a44c092f2c When a atom is reverted it can be useful to retain the result of that 'revert' method being called, so that it can be later analyzed (or used for various purposes) so adjust the storage, and actions to enable it to be stored. Change-Id: I38a9a5f3bf7550e924468bb4a86652cb8beb306c 
When a atom is reverted it can be useful to retain the
result of that 'revert' method being called, so that it
can be later analyzed (or used for various purposes) so
adjust the storage, and actions to enable it to be stored.

Change-Id: I38a9a5f3bf7550e924468bb4a86652cb8beb306c
Rename logbook module -> models module 2015-07-09T00:04:35+00:00 Joshua Harlow harlowja@yahoo-inc.com 2015-06-10T01:19:11+00:00 1e3dc09453e7e179fba613b61317ebad1556b77b Since this module contains more than the logbook class and really is a our generic models that are used to hold the runtime structure it is more appropriate to place it under a models module and deprecate the usage of the old module by placing a warning there (so that when it is imported that warning is triggered). Change-Id: I79def5ee08f560d38f2c9dcefd0b33becc2a4d36 
Since this module contains more than the logbook
class and really is a our generic models that are used
to hold the runtime structure it is more appropriate to
place it under a models module and deprecate the usage
of the old module by placing a warning there (so that
when it is imported that warning is triggered).

Change-Id: I79def5ee08f560d38f2c9dcefd0b33becc2a4d36
Fix updated_at column of sqlalchemy tables 2015-05-21T05:48:17+00:00 Fredrik Bergroth fbergroth@gmail.com 2015-05-20T18:24:01+00:00 e183fc9dbc101d10491a8b04bb73cfb789b8826c The column updated_at does not update its value after the refactoring made in 687ec913790653f79badc8f5d656c86792e94271. Closes-Bug: #1457309 Change-Id: Iff45f386b5dc8efc3fe82ca3b1e961a0c23d7ac7 
The column updated_at does not update its value after the refactoring
made in 687ec913790653f79badc8f5d656c86792e94271.

Closes-Bug: #1457309
Change-Id: Iff45f386b5dc8efc3fe82ca3b1e961a0c23d7ac7
Switch to non-namespaced module imports 2015-03-12T11:12:29+00:00 Davanum Srinivas davanum@gmail.com 2015-03-12T11:12:19+00:00 f6e20741638ff5ddc033a6338c374da35beb8c5d Change-Id: I25686df6a05bf69a89b9b6be169db72eab89d32a 
Change-Id: I25686df6a05bf69a89b9b6be169db72eab89d32a
Rework the sqlalchemy backend 2015-02-10T05:36:44+00:00 Joshua Harlow harlowja@yahoo-inc.com 2014-10-02T19:39:00+00:00 687ec913790653f79badc8f5d656c86792e94271 We can just simplify the usage of an sqlalchemy if we just use (we already have our own ORM like objects anyway) sqlalchemy core in the first place and have a very tiny layer that converts back and forth from our very limited object model that we use in our persistence layer. This change makes that adjustment, which makes it easier to read and understand the actions the sqlalchemy backend is doing when saving, reading and updating data, and avoids yet another layer that isn't useful for our purposes anyway. Change-Id: I911c509f65e7845aee86fed1622eaa56970741f2 
We can just simplify the usage of an sqlalchemy if we just use
(we already have our own ORM like objects anyway) sqlalchemy core
in the first place and have a very tiny layer that converts back and
forth from our very limited object model that we use in our
persistence layer.

This change makes that adjustment, which makes it easier to read
and understand the actions the sqlalchemy backend is doing when
saving, reading and updating data, and avoids yet another layer
that isn't useful for our purposes anyway.

Change-Id: I911c509f65e7845aee86fed1622eaa56970741f2