[Pulp-dev] Database support in Pulp 3

[Daniel Alley]

One more note:  Not all MySQL / MariaDB installations support transactions,
which we use heavily (and rely on?)

https://docs.djangoproject.com/en/2.2/topics/db/transactions/#transactions-in-mysql

On Thu, Jul 11, 2019 at 3:55 PM David Davis <daviddavis at redhat.com> wrote:

> Two plugins are currently running into issues trying to support
> mariadb/mysql. The pulp_ansible plugin is interested in adding full text
> search and JSONFields. Meanwhile, the pulp_python plugin is trying to store
> emojis in text which mariadb/mysql doesn't handle well since it uses 3-byte
> utf-8 by default[0]. Given such cases, I wonder if we'd be better served by
> dropping mariadb/mysql support and going with Postgresql only. Gitlab
> recently came to a similar conclusion[1].
>
> I personally am hesitant to give up being database agnostic but we already
> don't support sqlite. Also, I see some advantages like utilizing several
> Postgresql-only features like extra field types, full text search, etc.
> Also, supporting multiple databases means we'll likely have to write db
> specific code in some places or have plugins that only work with certain
> database types.
>
> Thoughts?
>
> [0]
> https://medium.com/@adamhooper/in-mysql-never-use-utf8-use-utf8mb4-11761243e434
>      https://code.djangoproject.com/ticket/18392
> [1] https://about.gitlab.com/2019/06/27/removing-mysql-support/
>
> David
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20190711/ee012c25/attachment.htm>