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

[DDC-2655] Don't let getOneOrNullResult throw NoResultException #780

Merged
merged 1 commit into from
Oct 11, 2013
Merged

Conversation

terite
Copy link
Contributor

@terite terite commented Sep 5, 2013

DDC-2655

@doctrinebot
Copy link

Hello,

thank you for creating this pull request. I have automatically opened an issue
on our Jira Bug Tracker for you. See the issue link:

http://www.doctrine-project.org/jira/browse/DDC-2656

We use Jira to track the state of pull requests and the versions they got
included in.

@terite
Copy link
Contributor Author

terite commented Sep 5, 2013


use Doctrine\ORM\Query;

require_once __DIR__ . '/../../../TestInit.php';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you remove this line? While many tests still have it, its actually not needed anymore.

@terite
Copy link
Contributor Author

terite commented Sep 13, 2013

Is this pull request now satisfactory?

@terite
Copy link
Contributor Author

terite commented Oct 2, 2013

How's this looking, @beberlei?

@terite
Copy link
Contributor Author

terite commented Oct 9, 2013

I combined the commits and rebased from the current master. Is anything wrong?

@stof
Copy link
Member

stof commented Oct 11, 2013

This looks good to me.

@guilhermeblanco @beberlei what do you think ?

guilhermeblanco added a commit that referenced this pull request Oct 11, 2013
[DDC-2655] Don't let getOneOrNullResult throw NoResultException
@guilhermeblanco guilhermeblanco merged commit bb63058 into doctrine:master Oct 11, 2013
@flack
Copy link
Contributor

flack commented Jun 5, 2017

This was fixed long ago, shouldn't the ticket (and PR #3391) be closed?

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