- 🇺🇸United States TomTech
Automatically closed because Drupal 7 security and bugfix support has ended → as of 5 January 2025. If the issue verifiably applies → to later versions, please reopen with details and update the version.
If two processes are acting on the same license at the same time, and both of them save revisions, then the revisions can be created out of order.
If:
Then the resulting revision table will look like:
revision_id revision_created revision_ended
1 124 0
2 123 0
That history would not make sense, because the created dates are out of order, and there are >1 open revisions.
Perhaps the best academic solution would be to create pessimistic locks when loading licenses for update.
This solution is a little unrealistic (see the problems with commerce_order locking in 📌 Improve commerce entities locking Needs review ).
The proposed solution is to prevent saving a license if another revision already exists with a simultaneous or later revision_created timestamp.
Closed: outdated
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Automatically closed because Drupal 7 security and bugfix support has ended → as of 5 January 2025. If the issue verifiably applies → to later versions, please reopen with details and update the version.