I may be betraying my inexperience with the project, but a question about this case:
Tue, May 7
Apr 7 2019
Apr 6 2019
Apr 5 2019
Mar 7 2019
Another option: overseer
Feb 27 2019
One potential library to help with this: go-update
Feb 24 2019
Feb 22 2019
Jan 24 2019
Jan 19 2019
Jan 18 2019
Jan 17 2019
Jan 10 2019
Jan 4 2019
Dec 31 2018
Dec 25 2018
Dec 14 2018
Need a little time to read into the "magic" that happens in this library, but certmagic might be the easiest way to implement this.
Dec 11 2018
Dec 10 2018
Have been testing more over the weekend -- no serious issues. Got this merged in and will release it today. Thanks again @benovermyer!
Dec 8 2018
Okay, did some more refactoring and caught some other errors / differences between MySQL and SQLite. Also added the SQLite option in the config setup.
Dec 6 2018
After this has been merged in, I'll work on the PostgreSQL support.
Dec 5 2018
Awesome. Plenty of people asking about that now, so that'll be good. If you want to take the charge on that one, please feel free!
Dec 3 2018
Oh, and I believe that adding PostgreSQL support will be much easier than SQLite. It should be able to use schema.sql and all of the MySQL SQL commands unmodified. The only bit that it'll require is a new connection block in the initial setup.
Dec 2 2018
Some feedback from my initial multi-user testing: so far almost everything looks solid, this is really good work! Only issue so far is something weird going on with scheduled posts. They correctly show as "scheduled" and don't show up for non-auth'd users. But once the published time has passed, the "scheduled" badge correctly drops for auth'd users, but the post doesn't show up for non-auth'd users like it should.
Dec 1 2018
Awesome!! I'll give it a thorough testing this weekend in various configurations and let you know how it looks.
Nov 27 2018
I have a working variation of schema.sql (called, appropriately enough, sqlite.sql) for SQLite.
Ah, gotcha. I thought there might be some differences when I was reading through this fork with sqlite support.
Nov 26 2018
As an example, SQLite doesn't support the SQL function NOW(). It also only has five data types - NULL, INTEGER, REAL, TEXT, and BLOB. Yes, that means boolean values are stored as full INTEGERs.
So as I've started testing this, I've discovered there is a vast chasm of differences between normal SQL and SQLite SQL. I'm working on the logic to handle both.
The working branch is here: https://github.com/writeas/writefreely/tree/sqlite-support
Ok cool 👍 let me know if you need anything along the way. Excited to get this in!
Actually, I retract my previous statement. I was thinking in terms of integration tests, not unit tests - the current pattern is fine.
Nice! I'm all for adding unit tests for database funcs -- especially with different databases, I agree we should make sure they work consistently.
I started working on a proof of concept for this yesterday morning. In the process, I noticed a couple things.