What about the integration tests that use database, you just run them synchronously?
D4no0
LostKobrakai
We run them synchronously, but due to the fact that our integration tests are heavy anyways and don’t really run much faster async.
1
sodapopcan
Ya, sqlite is crazy fast. It’s even recommended not to worry about N+1 since you’re reading from a consistently open file (not that you have a choice with Ecto, though).
0
warmwaffles
It consumes way more memory if you do all the preload magic that is encouraged for regular tcp database connections.
0
sodapopcan
Ah, that is good to know. I’m a recent sqlite convert and really loving it. I have high hopes for LiteFS. I guess there’s no elegant way around Ecto preloads, though? Obviously there is manually looping but I wouldn’t call that elegant 
I assume that would be a micro optimization anyway?
0
lindem
I have tried ecto in 2019, but it did not click with me back then. But I urgently needed mssql support, which also was not ready, so maybe it has not been ecto’s fault.
Now I want to try again. I still have nightmares from Hibernate and Entity Framework sometimes.
Do all of you not use generators? I resent form building and ui validation for CRUD. Do you all code these things by hand or is there something I should know other than generators?
0
warmwaffles
Yea I would just say to keep preloading as normal, but don’t worry too much about using Dataloader if you are using GraphQL. Just let it do N+1 loads.
1
warmwaffles
The only generator I use day to day is mix ecto.gen.migration everything else is build as I need it. None of the generators produce even close to what we have for our admin panel and structuring. That has been my experience with generators (rails, django, phoenix, etc…) for the last 8 years.
3
sodapopcan
Ya, I do by hand with help of editor snippets. For example I type defm<space> which expands to:
@impl true
def mount(_params, _session, socket) do
| # <- cursor
{:ok, socket}
end
and then type sa=<space> to get:
@impl true
def mount(_params, _session, socket) do
socket =
socket
|> assign(|)
{:ok, socket}
end
It’s actually recommended not to use the builtin generators for anything other than learning (sorry, I can’t find the citation). You end up tweaking them a bunch anyway. If you find yourself in a consistent pattern you like you can always make your own.
I’ve had the same experience as @warmwaffles… I use them for generating migrations and phx_new. I think that is pretty common!
2
LostKobrakai
Phoenix 1.7 improved the generators a lot, so it’s easier to adapt them to custom markup. But at some point I think many usecase outgrow what the generators could deliver (without customizing the generators templates).
0