[GH-ISSUE #51] Sqlite broken, rather just use MySql #47

New issue

Closed

opened 2026-02-26 01:35:00 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 01:35:00 +03:00

Owner

Originally created by @dagelf on GitHub (Jun 8, 2014).
Original GitHub issue: https://github.com/JLiscom/OpenNote/issues/51

After a shallow dig into the source, stil nevertheless almost an hour of my life spent on it... I've come to the conclusion that sqlite support is broken. Seems like all the sqlite debugging functions I last used aren't around anymore, and the only error message is "query failed" when trying to register. Too bad. I should've just gone with MySql from the start, was up in running in under 5 mins.

Ubuntu 14.04, apache, Sqlite 3.8.2, PHP 5.5.9

Originally created by @dagelf on GitHub (Jun 8, 2014). Original GitHub issue: https://github.com/JLiscom/OpenNote/issues/51 After a shallow dig into the source, stil nevertheless almost an hour of my life spent on it... I've come to the conclusion that sqlite support is broken. Seems like all the sqlite debugging functions I last used aren't around anymore, and the only error message is "query failed" when trying to register. Too bad. I should've just gone with MySql from the start, was up in running in under 5 mins. Ubuntu 14.04, apache, Sqlite 3.8.2, PHP 5.5.9

kerem

2026-02-26 01:35:00 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 01:35:01 +03:00

Author

Owner

@JLiscom commented on GitHub (Jun 9, 2014):

@dagelf
Sorry about that. My dev environment is in MYSQL. So that is what all the testing is done on.
We'll see if we cant get it back up for the next release

@JLiscom commented on GitHub (Jun 9, 2014): @dagelf Sorry about that. My dev environment is in MYSQL. So that is what all the testing is done on. We'll see if we cant get it back up for the next release