Mooodi
By default “timestamps()” generates a timestamp in naive datetime. When and when not will it be better to use “utc_datetime” instead?
In my app I need to use the values of “timestamps()”. And in some point I need to compare the “now()” with :inserted_at and then call DateTime.diff(…) I believe that it’s better for me to use :utc_datetime in “timestamps()” , right?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Bringing learning, work and compliance together since 1987.
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
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
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.
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 8 of 8 Posts
hubertlepicki
this has been on this forum quite a few times already (search for utc_datetime). In short: when you use Ecto only, this should not matter as it enforces client’s protocol to be in UTC time zone. However, it makes difference if you load scripts or perform queries using
psqlor other external tools, that can have different time zone settings.Mooodi
No. I’m calling
DateTime.diff(DateTime.utc_now(), my_article.inserted_at)in my app and it throws an exception because the “inserted_at” is Naive DateTimehubertlepicki
Ah, yes, this code will throw error unless you covert one type to another. I thought you meant SQL queries with “NOW()” function in them.
Mooodi
Hence, the answer to my question is – I should use :utc_datetime for “timestamps()”?
hubertlepicki
In my opinion - yes. That’s what I use and recommend to always use. (but opinions vary on this forum)
LostKobrakai
For as long as you’re not inserting the timestamps manually (e.g.
insert_all), but let ecto handle them you can basically switch them out at any time. Ecto does default toNaiveDateTime.utc_now(), so it’s going to be a utc datetime no matter what and on the db side there’s no difference between an:naive_datetimeand:utc_datetimefield.Mooodi
How can I convert “inserted_at” from naive to utc so that I can use it in DateTime.diff(…) ?
LostKobrakai
Either use
DateTime.from_naive!(a.inserted_at, "Etc/UTC")or setup your schemas to use:utc_datetime.