DDC-3681: [GH-1378] Feature to force-increment entity version #4524

Closed
opened 2026-01-22 14:44:04 +01:00 by admin · 6 comments
Owner

Originally created by @doctrinebot on GitHub (Apr 9, 2015).

Jira issue originally created by user @doctrinebot:

This issue is created automatically through a Github pull request on behalf of DHager:

Url: https://github.com/doctrine/doctrine2/pull/1378

Message:

Submitting for feedback and experimentation.

The major use-case for this involves using certain entities as the versioned-gatekeepers for changes that don't directly live on the same entity. For example, using the version of a PurchaseOrder to control changes to any of its child PurchaseOrderLineItem objects.

Originally created by @doctrinebot on GitHub (Apr 9, 2015). Jira issue originally created by user @doctrinebot: This issue is created automatically through a Github pull request on behalf of DHager: Url: https://github.com/doctrine/doctrine2/pull/1378 Message: Submitting for feedback and experimentation. The major use-case for this involves using certain entities as the versioned-gatekeepers for changes that don't directly live on the same entity. For example, using the version of a `PurchaseOrder` to control changes to any of its child `PurchaseOrderLineItem` objects.
admin added the New Feature label 2026-01-22 14:44:04 +01:00
admin closed this issue 2026-01-22 14:44:04 +01:00
Author
Owner
@doctrinebot commented on GitHub (Apr 9, 2015): - depends on [DDC-3683: [GH-1380] Fix issue with second-level-cache tests and versioned entities](http://www.doctrine-project.org/jira/browse/DDC-3683) - is duplicated by [DDC-3640: Force version increment via mapped property](http://www.doctrine-project.org/jira/browse/DDC-3640) - relates to [DDC-3781: Fix Optimistic Locking Scenarios for Versioned Entities in Bidirectional Relationships](http://www.doctrine-project.org/jira/browse/DDC-3781)
Author
Owner

@doctrinebot commented on GitHub (May 18, 2015):

Comment created by @doctrinebot:

A related Github Pull-Request [GH-1378] was closed:
https://github.com/doctrine/doctrine2/pull/1378

@doctrinebot commented on GitHub (May 18, 2015): Comment created by @doctrinebot: A related Github Pull-Request [GH-1378] was closed: https://github.com/doctrine/doctrine2/pull/1378
Author
Owner

@doctrinebot commented on GitHub (May 18, 2015):

Comment created by @doctrinebot:

A related Github Pull-Request [GH-1378] was reopened:
https://github.com/doctrine/doctrine2/pull/1378

@doctrinebot commented on GitHub (May 18, 2015): Comment created by @doctrinebot: A related Github Pull-Request [GH-1378] was reopened: https://github.com/doctrine/doctrine2/pull/1378
Author
Owner

@doctrinebot commented on GitHub (Jun 18, 2015):

Comment created by @zeroedin-bill:

This PR is not a suitable solution for the problem and is being closed. Please see DDC-3781 for a discussion of the issue and proposed solution.

@doctrinebot commented on GitHub (Jun 18, 2015): Comment created by @zeroedin-bill: This PR is not a suitable solution for the problem and is being closed. Please see [DDC-3781](http://www.doctrine-project.org/jira/browse/DDC-3781) for a discussion of the issue and proposed solution.
Author
Owner

@doctrinebot commented on GitHub (Jun 18, 2015):

Comment created by @doctrinebot:

A related Github Pull-Request [GH-1378] was closed:
https://github.com/doctrine/doctrine2/pull/1378

@doctrinebot commented on GitHub (Jun 18, 2015): Comment created by @doctrinebot: A related Github Pull-Request [GH-1378] was closed: https://github.com/doctrine/doctrine2/pull/1378
Author
Owner

@doctrinebot commented on GitHub (Jun 18, 2015):

Issue was closed with resolution "Won't Fix"

@doctrinebot commented on GitHub (Jun 18, 2015): Issue was closed with resolution "Won't Fix"
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#4524