Matthew Johnston
Matthew Johnston
> We don't support the Arch package. If they're going to build and package it their own way, they should also include the utility scripts. Yes, and that is apparent...
I wonder what the drawback is for using `BEGIN CONCURRENT` all the time is.
It's a shame that `BEGIN CONCURRENT` isn't implied because the WAL mode is enabled signalling that it would be a potentially concurrent database.
> Personally, I'd prefer running the official releases. This is generally my feelings as well. I haven't followed this feature too closely and don't know if it is going to...
I would love to use `memory` for the database, but with how the connections are pooled, that is impossible to do. Once the connection goes idle, it closes the database...
> Even if so, on re-open, after_connect would be executed again (running the migrations) There will be people who use a structure.sql as well and don't build from scratch completely....
If you run into any issues with `ecto_sqlite3` don't hesitate to drop an issue https://github.com/elixir-sqlite/ecto_sqlite3
heh this is a common problem with sqlite. There is no true datetime primitive. So if you wanted to do datetime comparisons, you have to explicitly cast it as you...
I do believe we _could_ handle the datetime comparisons behind the scenes. I would just need to setup some tests to replicate what you are doing to validate.
@sorentwo It appears to just work https://github.com/elixir-sqlite/ecto_sqlite3/commit/707fe8ec0dc9a0798f1fe8dd7533ebb1d84ae778 Are you sure you can't do `|> where([j], j.inserted_at >= ^since))`?