Please support sqlite

[jvoisin]

It would be great to support sqlite as database backend:

• It's already a dependency, for search
• My small instance doesn't need (nor want) a complete MySQL server
• It'll ease the backups
• It shouldn't have an impact on performances
• It'll ease the installation process

[ssddanbrown]

Hi @jvoisin, Sqllite is not currently a dependency, even for search. I can see how sqlite may be better for smaller instances though. The new changes to the search system makes support for sqlite much more possible now.

I just had a go (b30ee10) but it is going to take some additional care to implement, Don't really want to do this right before a release. Need to also consider the additional amount of work and support this will need going forward. It's close similarities to MySQL helps though.

[jvoisin]

Damn, I misread the ticket about the possibility of using sqlite for plain-text search, sorry.

Thank you for considering this ♥

[ssddanbrown]

Just in-case someone is interested in this feature, More in-depth conversions about non-MySQL support can be found in #76.

[partoneoftwo]

What would be the first steps to developing SQLite support?

[ssddanbrown]

@partoneoftwo In regards to the technical aspect, It'd be a case of adding in the sqllite part of the default laravel config into the similar BookStack file, updating the config to point at a sqllite db, then migrate and fix any issues from there.

In regards to getting support into the project, It would require my faith in a longer term contributor. I've detailed my feelings for additional DB support here:
#76 (comment)

My feelings remain much the same.

[partoneoftwo]

Thanks for the thoughts.
This does not seem like an unfeasible set of steps.

About the error messages:
Regarding the error messages listed in #617, to me do not seem severe. Curiously and interestingly the SQLite errors are the same as the errors which were encountered when trying out MSSQL #1493. Solve that one, and it's one step closer to just having the Laravel Db-Migration take care of the persisting to the data layer.

Sidenote:
I just had a slightly nasty DB issue, owning to myself sort of not paying attention to my webhosting for almost a year. Bad idea! Since the data in my BookStack instance is so critical, I spend a lot of energy trying to get it to work. My hunch is that this would have been a lot simpler on SQLite. And of course it would be much lighter to host.

[RGdevz]

+1

[Codefor4learn]

May I ask if we are still considering supporting sqlite

[mac641]

+1

[virtadpt]

Diversity in database back-ends is good.