Motivation: Paddle sometimes sends us two webhooks at the same time when a subscription is updated. We only need to count the latest one of those, for which we need more precision than 1s.
The migration will set both inserted_at and updated_at columns in the subscriptions table to use the :naive_datetime_usec type instead of just :naive_datetime. In practice, we currently need more precision only on the updated_at field. But I suppose it's better to keep the type between both timestamp fields consistent.
Changes
Motivation: Paddle sometimes sends us two webhooks at the same time when a subscription is updated. We only need to count the latest one of those, for which we need more precision than 1s.
The migration will set both
inserted_atandupdated_atcolumns in thesubscriptionstable to use the:naive_datetime_usectype instead of just:naive_datetime. In practice, we currently need more precision only on theupdated_atfield. But I suppose it's better to keep the type between both timestamp fields consistent.Tests
Changelog
Documentation
Dark mode