dipth
How does one go about storing datetime values from a date_select field in the database?
Here is my Ecto model:
defmodule MyApp.User do
use MyApp.Web, :model
schema "users" do
field :birthday, :utc_datetime
end
def changeset(struct, params \\ %{}) do
struct
|> cast(params, [:birthday])
end
end
Here is my template:
<%= date_select f, :birthday, builder: fn b -> %>
<%= b.(:day, prompt: "", class: "custom-select") %> /
<%= b.(:month, prompt: "", class: "custom-select") %> /
<%= b.(:year, options: Timex.now.year..(Timex.now.year - 100), prompt: "", class: "custom-select") %>
<% end %>
Here is my controller:
def update(conn, %{"user" => user_params}) do
user = Guardian.Plug.current_resource(conn)
changeset = User.changeset(user, user_params)
case Repo.update(changeset) do
{:ok, _user} ->
conn
|> put_flash(:success, gettext("Profile updated!"))
|> redirect(to: public_profile_path(conn, :show, user))
{:error, changeset} ->
conn
|> render("edit.html", changeset: changeset)
end
end
I can successfully submit the form, but the birthday is never written to the database
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Courses that'll move you from confusion to "Aha, now I get it!"
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
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 4 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
dipth
You are right. Changing the column in the database to
:datefixes the problem.I find it weird though that it shouldn’t be possible to store a date value in a datetime field and just have the time-part assumed as midnight.
In this case it isn’t a big problem, but there might be cases where it is important to have the time-part in the database as well as the date in case you want to perform timezone-sensitive checks on the date…
dsissitka
I wonder if you need to use
field :birthday, :date.I wonder if that’s because you’re using
:utc_datetimeand you aren’t passing in a time.dipth
It appears that there is some sort of implicit validation taking place since
f.errors[:birthday]in the template returns “is invalid”I have also tried using Timex like so:
which just gives an error:
Trying with a Timex date field instead:
gives another error:
radar
What do the logs show when that action is hit?