juliolinarez
I realized that Ash generates timestamps in the application, which is what I want. To be sure, I removed the default values for those fields in the database migration. However, now when I run mix ash_postgres.generate_migrations, it wants to add a default value back in the snapshot files.
How can I prevent this?
attributes do
attribute :id, :uuid do
primary_key? true
allow_nil? false
default &UUIDv7.generate/0
end
attribute :title, :string do
allow_nil? false
end
attribute :content, :string do
allow_nil? false
end
create_timestamp :inserted_at
update_timestamp :updated_at
end
Is there a way to prevent that globally?
Thank for this amazing framework 
Im using: ash 3.5.33, ash_postgres: 2.6.14, phoenix:1.7.21
Where Next?
Trending in Discussions
Other Trending Topics
Latest Ash Threads
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
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.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
ken-kost
Looking at the docs, you should be able to set the default of the timestamp attributes to nil.
To have it global you would need to make your own dsl and use that. Or just use attribute.
juliolinarez
Sorry, I meant leaving it with a default of
nilat the database level, but defining the default in Ash instead. That way,mix ash_postgres.generate_migrationswon’t keep generating changes inresources_snapshotsfor it.ken-kost
If I’m not mistaken, I think the default is the fragment added.
zachdaniel
Is there a particular reason you don’t want the database default? You can have both just fine in general, application-side defaults and database defaults.
juliolinarez
Now that I think about it, it’s just a habit. I’m used to lowering the database’s CPU usage, and I liked making sure Elixir was the one generating the default values. But now that you mention it, I could check the SQL logs for that.
zachdaniel
Yeah ultimately it should be safe to have it in both places, and acts as a benefit for retaining application behavior even when data is inserted directly into the database.