tiagodavi
Hey Guys. I would like to ask a couple of questions about Ecto and Async tasks.
1 - Are there plans to improve the way we use Ecto + Async Tests + Async Code? Using SQL.Sandbox is in IMHO really confusing.
2 - Are there best practices to use async tests + async code ?
3 - Let’s imagine I have a GenServer Process that inserts 1000 lines each hour using Repo.insert instead of using Repo.insert_all. Would that be a problem to kill my process and my entire application? Does Ecto try to get a new connection from database pool for each insert using Repo.insert?
4 - Let’s imagine I have a async task in my code that does not matter that result to the user, but I want to test it. Should I send a message to the parent process to use assert_receive?
Thank you in advance.
Trending in Questions
Other Trending Topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixir-ls
- #ai
- #elixirconf-us
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
hauleth
SQL.Sandbox(especially fact that everything is ran within single transaction, which allows asynchronous testing with Postgres).Ecto.Adapters.SQL.Sandbox.Repo.transactionorRepo.checkouttiagodavi
Thank you!