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.

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

order found snapshots by publicationDateStart #387

Closed
wants to merge 1 commit into from
Closed

order found snapshots by publicationDateStart #387

wants to merge 1 commit into from

Conversation

koyaan
Copy link

@koyaan koyaan commented Sep 8, 2014

It is counterintuitive that if more then one snapshot matches the date criteria, the one that was created first is selected, it should be the one with the newest startDate.

@rande
Copy link
Member

rande commented Sep 8, 2014

This is a major BC break ?

@koyaan
Copy link
Author

koyaan commented Sep 8, 2014

It is? why can we even have multiple matching snapshots?

@koyaan
Copy link
Author

koyaan commented Sep 9, 2014

@rande if this will never be merged because it is too big of a BC i will close and just use my fork for my projects. But feedback from people using it, is highly in favor of this change since the need to manually delete or deactivate older snapshots makes the ux much more complicated and error prone.

@OskarStark
Copy link
Member

This is BC because you set $query->setMaxResults(1);

@soullivaneuh
Copy link
Member

This is BC because you set $query->setMaxResults(1);

I don't think so. This code part is already here.

@OskarStark
Copy link
Member

yes, but it changed the behavior/result by sorting it another why, doesn't it?

@core23 core23 added this to the 3.0 milestone Feb 11, 2016
@soullivaneuh
Copy link
Member

According to the new Sonata version management and next major release plan, this project has been refactored regarding branching and versioning.

If you see this message, your PR concerns a patch or a minor release and is not targeting the right branch.

So I'm closing this one, but don't see it as a refusal. If you think your work is still relevant and want to continue, feel free to reopen it on the right branch (e.g. the default one).

Regards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants