Perhaps. In the current code base I am working on day to day, we have 890 migrations and rising. The quickest and best solution is to use mix ecto.dump and mix ecto.load. We aren’t using sqlite, but there is a limit to running migrations front to back every time a connection is checked out. You’ll definitely want to load the schema.
warmwaffles
0
fceruti
I’ve got this test case where a new random directory is created for each test, I also use it for sqlite3, but the scenario is somewhat different.
To cover your use case, I would:
- Create a database file and migrate it before running any tests. Store somewhere.
- Modify the snippet below to copy the fresh database before every test.
defmodule MyApp.SandboxCase do
use ExUnit.CaseTemplate
@symbols ~c"023456789abcdefghijklmnopqrst"
@n_symbols Enum.count(@symbols)
setup do
rand_dir = for _ <- 1..20, into: "", do: <<Enum.at(@symbols, :rand.uniform(@n_symbols))>>
sandbox_dir = "/tmp/sandbox/#{rand_dir}/"
pid = self()
ref = make_ref()
spawn_link(fn -> monitor_for_cleanup(pid, ref, sandbox_dir) end)
receive do
{^ref, :ready} -> :ok
end
on_exit(fn ->
File.rm_rf(sandbox_dir)
end)
%{sandbox_dir: sandbox_dir}
end
defp monitor_for_cleanup(pid, ref, path) do
Process.flag(:trap_exit, true)
send(pid, {ref, :ready})
receive do
{:DOWN, ^pid, _reason} ->
File.rm_rf(path)
end
end
end
**
0
warmwaffles
Test generation is not in the purview of ecto_sqlite3 or exqlite that is something in phoenix proper. You will need to submit a PR or open an issue there about it. The ecto_sqlite3 dependency does not provide generators.
0
sodapopcan
I don’t use generators but I’m interested as I’m developing a (small) app slated for production using sqlite.
Are there any missing steps to reproduce? I generated a new project and generated two contexts using phx.gen.live. I copied in the routes and ran tests maybe 20 times in a row and never got a failure. Maybe OS matters? I’m on latest macos.
0
warmwaffles
lindem
I am on linux as well. I have created the project with
Erlang/OTP 25 [erts-13.0.4] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [jit:ns]
Elixir 1.15.4 (compiled with Erlang/OTP 25)
versions I used:
# Type `mix help deps` for examples and options.
defp deps do
[
{:bcrypt_elixir, "~> 3.0"},
{:phoenix, "~> 1.7.7"},
{:phoenix_ecto, "~> 4.4"},
{:ecto_sql, "~> 3.10"},
{:ecto_sqlite3, ">= 0.0.0"},
{:phoenix_html, "~> 3.3"},
{:phoenix_live_reload, "~> 1.2", only: :dev},
{:phoenix_live_view, "~> 0.19.0"},
{:floki, ">= 0.30.0", only: :test},
{:phoenix_live_dashboard, "~> 0.8.0"},
{:esbuild, "~> 0.7", runtime: Mix.env() == :dev},
{:tailwind, "~> 0.2.0", runtime: Mix.env() == :dev},
{:swoosh, "~> 1.3"},
{:finch, "~> 0.13"},
{:telemetry_metrics, "~> 0.6"},
{:telemetry_poller, "~> 1.0"},
{:gettext, "~> 0.20"},
{:jason, "~> 1.2"},
{:plug_cowboy, "~> 2.5"},
{:credo, "~> 1.7", only: [:dev, :test], runtime: false}
]
end
Hmm, I can try on another machine if it happens there as well. Surprising.
0
warmwaffles
lindem
I have generated a fresh one, still exhibiting the problem, and put it at GitHub - lindem/sqlite3_testsetup: SQLite3 failure example application · GitHub
Thanks very much for looking into this!
0
sodapopcan
Ah ha, it’s because you didn’t pluralize your table name. It’s throwing off the generator.
I was able to reproduce with:
$ mix phx.gen.live Things Thing thing thingvalue:integer thingdescription:string
as in your example.
$ mix phx.gen.live Things Thing things thingvalue:integer thingdescription:string
works just fine.
5