ecto

The documentation for the Phoenix scrub_params method is a little unclear to me. It seems like this functionality is similar to the Rails strong parameters feature. However, when you use it in a controller like so, plug :scrub_params, "user" when action in [:create] ... you're not explicitly stating which parameters you want to whitelist. I've looked at the code for scrub_params , but I'm noobish enough with Elixir that I'm not quite sure what's going on. Is this method just looking at the model and using the required and optional field module attributes for whitelisting parameters? Also, the

In Elixir, the pin operator is used to prevent variable rebinding. However, with regard to an Ecto query like from u in User, where: u.username == ^username the authors of Programming Phoenix state (in chapter 7) that Remember, the ^ operator (called the pin operator) means we want to keep ^username the same. But this doesn't sound right, because apparently, the comparison in the query shall not cause any rebinding of variables. Are the authors of the book (which José Valim co-authored) mistaken? Is the pin operator in Ecto queries merely a construct of the Ecto DSL instead of a usual Elixir

I have a schema: schema "editables" do field :title, :string field :content, :string timestamps end Now I want to change the type of one field form :integer to :binary . What's the correct way of writing the migration because using add is not working...? def change do alter table(:editables) do add :title, :binary add :content, :binary timestamps end end You have to use modify/3 to change the type. add/3 is only for adding new columns. alter table(:editables) do modify :content, :binary end 来源： https://stackoverflow.com/questions/32583625/how-to-change-field-type-in-ecto

I am building an Ecto query like this: from item in query, where: like(item.description, ^"%#{text}%") I'm concerned that this allows SQL injection in text . Before trying to fix that, I want to see how the query is actually sent to the database. If I inspect the query or look at what is logged, I see some SQL, but it's not valid. For instance, inspecting the query shows me this: {"SELECT i0.\"id\", i0.\"store_id\", i0.\"title\", i0.\"description\" FROM \"items\" AS i0 WHERE (i0.\"description\" LIKE $1)", ["%foo%"]} When I pass this query to Repo.all , it logs this: SELECT i0."id", i0."store

I recently upgraded my phoenix project to Ecto 2.0.2. I have some code that is using Task.Supervisor.async_nolink to make some updates to the db on its own thread. I am getting the following error when my tests run (only occurs on my tests) [error] Postgrex.Protocol (#PID<0.XXX.0>) disconnected: ** (DBConnection.ConnectionError) owner #PID<0.XXX.0> exited while client #PID<0.XXX.0> is still running with: shutdown Now I think I understand whats happening: The Ecto Sandbox connection pool is being checked back in before the db transaction is complete. According to the docs (at least the way I

I am trying to implement permalinks in phoenix app. The goal is to change localhost:4000/products/1 to localhost:4000/products/productname I tried following Ryan Bates episode on permalinks implementation in rails but wasn't able to find a to_param function for models in phoenix. Please help. Not sure if this is what you are asking for but here you go: router.ex in the browser stack get "/products/:product_name", ProductController, :get_product_by_name product_controller.ex def get_product_by_name(conn, %{"product_name" => product_name}) do product = Repo.get_by(Product, name: product_name)