Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider taking order in collection navigations into account for update pipeline topological sort #319

Closed
rowanmiller opened this issue Jun 16, 2014 · 1 comment
Closed

Consider taking order in collection navigations into account for update pipeline topological sort #319

rowanmiller opened this issue Jun 16, 2014 · 1 comment
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-unknown
Milestone
1.0.0

Comments

@rowanmiller
Copy link
Contributor

Originally discussed on CodePlex - https://entityframework.codeplex.com/workitem/2342.
It may be interesting to take the order of items in collection navigation properties into account when ordering things for CUD operations (when the collection type has an order).
@rowanmiller rowanmiller modified the milestones: 1.0.0-alpha3, 1.0.0-alpha4 Aug 20, 2014
@divega divega changed the title Consider taking order in collection navigations into account for update pipeline topilogical sort Consider taking order in collection navigations into account for update pipeline topological sort Sep 16, 2014
@bricelam bricelam modified the milestones: 1.0.0-alpha4, 1.0.0-beta1 Oct 6, 2014
@rowanmiller
Copy link
Contributor Author

We decided not to do this.

@ajcvickers ajcvickers added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label Oct 15, 2022
@ajcvickers ajcvickers modified the milestones: 1.0.0-beta1, 1.0.0 Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-unknown
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
3 participants
@bricelam @ajcvickers @rowanmiller