On Tue, 19 Nov 2024 01:19:37 +0100,
Kirill A. Korinsky <kirill@korins.ky> wrote:
> 
> On Mon, 18 Nov 2024 23:42:01 +0100,
> Volker Schlecht <openbsd-ports@schlecht.dev> wrote:
> > 
> > On 2024-11-18 18:17, Kirill A. Korinsky wrote:
> > > ports@, Volker,
> > > 
> > > To make using of net/ejabberd better, we need a support of ODBC at erlang.
> > 
> > Are you positive about that? 
> > https://docs.ejabberd.im/admin/configuration/database/#sql-options
> > 
> > This reads as if there's native Postgres and MySQL interfaces... wouldn't those
> > be enough?
> > 
> 
> Thanks to point it. I haven't tried Postgres and MySQL, but I almost sure
> that when I had to try to use it, and it complains that it can't start odbc.
> 
> But, I just enabled it on my cluster (I mean sqlite), and it works without
> any issue.
> 
> Seems that it's enough. But I will wait a few days before I say that it's
> enough.
>

And here it is:

        2024-11-19 01:40:16.246908+01:00 [critical] <0.647.0>@ejabberd:exit_or_halt/2:158 Failed to start Erlang application 'odbc': no such file or directory: odbc .app. This usually means that ejabberd or Erlang was compiled/installed incorrectly.
        2024-11-19 01:40:16.247055+01:00 [error] <0.647.0>@ejabberd_hooks:safe_apply/4:460 Hook user_receive_packet crashed when running mod_mam:user_receive_packet /1:

My point: Postgres and MySQL, both, require setup. Mnesia and sqlite works
out of the box. Mnesia nice DB but it is used for message archive by default
and it will be broken, as soon as size hit 2Gb. I think that we should
enable sqlite for message archive by default, because migration from Mnesia
to anything is tricky, and allow users to have an explosion when their DB
reach 2Gb isn't good idea.

-- 
wbr, Kirill