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.

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.

Thanks @bkoehn! A lot of people have their eyes on the Docker setup right now, but for now @benovermyer has taken the reins on it. What other kinds of build integrations could you help with?