As pointed out in https://github.com/fossasia/eventyay-tickets/pull/98#issuecomment-2123539094, the django-mysql being used doesn't have the connection_is_mariadb function and even though there were efforts to remove that it seems dependencies were not adjusted accordingly. It seems like django-jsonfallback is actually not compatible with the version we use of django-mysql due to the connection_is_mariadb dependency, even at its latest version.
As pointed out in https://github.com/fossasia/eventyay-tickets/pull/98#issuecomment-2123539094, the
django-mysqlbeing used doesn't have theconnection_is_mariadbfunction and even though there were efforts to remove that it seems dependencies were not adjusted accordingly. It seems likedjango-jsonfallbackis actually not compatible with the version we use ofdjango-mysqldue to theconnection_is_mariadbdependency, even at its latest version.However it seems like #diff-39276994c50b9f2771c0cffec4886e775edcf1c739f13fca75c4c406340119b7 introduced a replacement for
[django-jsonfallback](https://github.com/raphaelm/django-jsonfallback/tree/master)functions but missed removing the dependency. Doing it here.Note that this is untested and only fixing
django-jsonfallbackthere might be other inconsistent dependencies.