embedded MySql alternatives

[Soren Harward]

Sorry, I meant "baloo's scanning capabilities, which are much better than
strigi's were."

--
Soren Harward
stharward at gmail.com

On Mon, Jan 6, 2020, 11:02 Soren Harward <stharward at gmail.com> wrote:

> I've done testing with SQLite in other applications, and I don't think the
> problems we had with it 10 years ago are relevant anymore due to
> improvements in both hardware and software. I've got a private branch where
> I started porting Amarok's code over to SQLite a couple of years ago, but
> didn't finish it. It's still a worthy goal.
>
> The other thing I started doing in that branch is using baloo for file
> scanning and metadata extraction, with only Amarok-specific data like play
> counts stored in the SQLite DB. That, I think, is the best way to go so
> Amarok doesn't duplicate strigi's pretty good scanning capabilities.
>
> --
> Soren Harward
> stharward at gmail.com
>
> On Mon, Jan 6, 2020, 10:31 Myriam Schweingruber <myriam at kde.org> wrote:
>
>> Hi Leo,
>>
>> On Sun, 5 Jan 2020 at 10:11, subscription1 <llsubscr at zudiewiener.com>
>> wrote:
>>
>>> Given that the embedded MySql has disappeared from the latest Ubuntu
>>> release the only other alternative to install Amarok on this (and later)
>>> releases I can see is to
>>>
>>>    1. Make amarok installation dependant on a MySQL server installation
>>>    2. Use something like Sqlite as the default
>>>
>>> I don't really have a solution, but I know we deliberately changed from
>> SQLite wich was default in Amarok 1.x to MySQL embedded with the option of
>> MySQL Server due to the bad scaling of SQLite. Many users of Amarok
>> requested that change, some having enormous databases that were very
>> slow to handle with SQLite.
>>
>> We probably have to choose the first option, but giving the users the
>> option to use an existing MySQL server installation or creating one just
>> for Amarok. There also is software in place (probably outdated) to use
>> Akonadi which we waited to get usable before adopting it, something which
>> even Kmail is still struggling with, unless Akonadi is used with PostgreSQL.
>> Of course another option would be to change to PostgreSQL which scales
>> quite well and might be a better solution. This looks like something we
>> would need to ask the users TBH.
>>
>> Regards, Myriam
>>
>> PS. Unless we find a better embedded database system, of course...
>> --
>> Proud member of the Amarok and KDE Community
>> Protect your freedom and support the work of the FSFE:
>> http://www.fsfe.org
>> <http://www.fsfe.org/>
>> Please don't send me proprietary file formats,
>> use ISO standard ODF instead (ISO/IEC 26300)
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/amarok-devel/attachments/20200106/4d063e5e/attachment-0001.html>