When doing these kinds of migrations against big databases, this can cause long downtime. We need to investigate if we can move from columns to pivot tables, as they don't have this problem.
For the payment fee columns I don't see a big issue with this, this is more with the mollie_transaction_id that is being wildly used where I can see that it could give some errors.
When we do this, I would expect a major version bump to let people know something big has changed.
Right now we add several columns to different kinds of tables:
When doing these kinds of migrations against big databases, this can cause long downtime. We need to investigate if we can move from columns to pivot tables, as they don't have this problem.
For the payment fee columns I don't see a big issue with this, this is more with the
mollie_transaction_id
that is being wildly used where I can see that it could give some errors.When we do this, I would expect a major version bump to let people know something big has changed.