Max
Hi,
after changing a field type or the length of the field. We see users getting the following error:
ERROR 0A000 (feature_not_supported): cached plan must not change result type
This error seems to show up only once though. After a refresh of the page, the error is gone.
It hits the user who first hits a certain route. So there seems to be some cache involved there the old type / length collides with the new one.
What can i do?
thank
Trending in Questions
Hello everyone!
I am new to coding with Elixir/Erlang. And i am looking for some utilities for fuzzing testing like AFL++.
Does anyone ...
New
I’m very new to Elixir, so sorry if this is a silly question:
I am wondering what happens to the mailbox of a process when the machine i...
New
How do I tell Hologram not to escape HTML when substituting into templates?
{Textile.render(@product.long_description)}
escapes the HTM...
New
I load tested a plain Phoenix chat app backed by Postgres with 100 million messages in it, everything on default settings, to see what br...
New
Background
When trying to execute mix release on a Windows 11 machine for a Phoenix project I get the following error:
* assembling mark...
New
I’d like to create a file with 600 permissions (rw-------), but there’s a race condition if I create it and then change the permissions. ...
New
Is there a way to import record definitions in the iex shell for pretty printing (similar to the rr command in the erl shell)? This woul...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #elixirconf-us
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #elixirconf-eu
- #security
- #processes
- #api
- #forms
- #hex










Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Eiji
@Max: This error happens if for example you run application and in another terminal you change any table. I think that you have application already started and executed
mix ecto.migrate. You need to restart app or your connection to database after migration finishes, but I don’t know when to detect it. I suggest to not complicate it and simply restart application.Max
Thanks for the input. But it seems that only a db (aws rds) restart seems to solve the problem. Restarting the app or even the app server didn´t help.
Eiji
@Max: hmm, strange
I found solution for it at: stackoverflow.
I don’t know what you exactly do, but I through about:
I don’t know what deployment tools you were using, but from what I can imagine you only need to restart your app (or maybe proxy if any) that holds connection to database. Once your app setups new connection your app should see new database structure.
Another words: you do not need to restart database after you call
MIX_ENV=prod mix ecto.migrate(when your app is not started), do you?So you only need to restart connection between your app and database. What you were doing is permanent close all connections to that database. Maybe there was a connection cache (remember database structure for IP?) or something, but in normal case you do not need to restart Amazon RDS or maybe you are using “special” database that needs a restart. Out of curiosity: what database are you using for that application? I don’t have such a problem with latest PostgreSQL.
Max
For deployment i use Distillery. I´m almost sure i´ve tried to restart the app without any success. Perhaps the restart itself didn´t work without getting noticed by me. I will try your advice next time again.
Thanks