We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The schema is using the string type value for the message which means for long message the value can't be saved and postgres returns an error: https://github.com/dwyl/phoenix-liveview-chat-example/blob/f4812190ac7f9620a6244f91c00e1d2425170dae/priv/repo/migrations/20211122121548_create_messages.exs
string
message
We can either use a differnt type for the field: https://hexdocs.pm/ecto_sql/Ecto.Migration.html#module-field-types
Or display an error on the client. It is easy to add a new migration to update the field type and I'm tempted to go in that direction
The text was updated successfully, but these errors were encountered:
Update message ecto type
c8aa510
Use :text instead of :string to allow long text as message see: #149
SimonLab
No branches or pull requests
The schema is using the
string
type value for themessage
which means for long message the value can't be saved and postgres returns an error:https://github.com/dwyl/phoenix-liveview-chat-example/blob/f4812190ac7f9620a6244f91c00e1d2425170dae/priv/repo/migrations/20211122121548_create_messages.exs
We can either use a differnt type for the field:
https://hexdocs.pm/ecto_sql/Ecto.Migration.html#module-field-types
Or display an error on the client. It is easy to add a new migration to update the field type and I'm tempted to go in that direction
The text was updated successfully, but these errors were encountered: