I'm fine with discarding it (since said support is only for posgres
anyway afaik), if it's causing issues for (packaging) folks and nobody
else in openstack really uses it either.
Let's see what folks think,
On another note (if not many projects are using it); I think it would be
nice to try to use it more in other projects, since afaik mysql and
postgres are both getting/now have native json support and afaik
sqlalchemy-utils is the current way to support said native types. And a
lot of openstack stores json blobs (metadata...) in text fields (when
they really could start to move toward the native json field types) so
its usage would seem appropriate,
But if it's to much of a pain to package for not much adoption, then
that's ok to.
-Josh
On 02/12/2016 12:57 PM, Corey Bryant wrote:
Are any projects using sqlalchemy-utils?
taskflow started using it recently, however it's only needed for a
single type in taskflow (JSONType). I'm wondering if it's worth the
effort of maintaining it and it's dependencies in Ubuntu main or if
perhaps we can just revert this bit to define the JSONType internally.
--
Regards,
Corey
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
