SQLite backend

[felipe19930]

What problem is this solving

Simplifying installation and usage for regular users.

Proposed solution

Having a SQLite backend would simplify greatly the installation and usage for users.

SQLite is arguably lighter (disk space wise) than PostgreSQL, and doesn't require a server service running, or setting up passwords.

Describe alternatives you've considered

No response

[leakedby]

Yes, why not Sqlite?

[H1ghSyst3m]

SQLite would be so good, because the database can then also be saved then if you have to change or reset computer. The Database would be portable then

[felipe19930]

@akiver I see you seem to have no interest in this, but if someone else were to implement this, and then send their work for review through a pull request, would you even consider accepting it?

[jamezmoran]

Any thoughts on why postgres exactly is the default here? I'm looking at the code now and so far don't see any reasons this can't be ported to SQLite, @akiver appears to have taken care to not encumber the app in postgres specific things which is good. Just trying to understand where the sticking points are incase I (or someone else) might want to knock this out in a week, if that's even possible.

[ShiinaKin]

Agree. IMO, it's not difficult to resolve this problem, maybe just add a setting page to choose which Database he want to use, and use correspondingly driver to implement it at the low level. But I'm a Java programmer, maybe in Node do this will be difficult, otherwise I can't think of any reason why shouldn't do this.

[LouisAsanaka]

I'd be willing to give it a shot when I'm free, provided that @akiver approves of the inclusion of SQLite :)

[alirezanet]

Postgres db?! is the worst choice ever :) !!!!!!!

[guixxx]

+1 for a lighter database backend.

PostgreSQL using almost 4x more disk space than the actual app is ludicrous.

[FalkF]

@akiver I feel like with minimal input many people could end up happy long term ;)