DDC-1822: Intermediary parent for NoResult and NonUnique Exceptions #2293

New Issue

admin · 2026-01-22T13:47:33+01:00

admin commented

2026-01-22 13:47:33 +01:00

Originally created by @doctrinebot on GitHub (May 16, 2012).

Originally assigned to: @guilhermeblanco on GitHub.

Jira issue originally created by user rdohms:

I would like to propose a intermediary parent for the NoResult and NonUnique Exceptions, that is not as high level as ORMEXception, something in between.

The reasoning for this is that sometime si want to get a single object out of the DB, and in case its not there i want to just get a null and carry on. For this I usually need to catch both exceptions as both results might trigger me to do something else, like abort. In some cases i do need to treat each of these in its own way, but in some cases it does not matter to which side the error went, it only matters that its not the expected SingleResult. Catching a ORMException is not adequate as it may include other error which would need to be treated differently.

My proposal would be like:

ORMException -> NotExpectedResultException -> {NoResult, NonUnique}

Just a more detailed grouping of exceptions. Does this sound like something possible, or am I just nuts?

Originally created by @doctrinebot on GitHub (May 16, 2012). Originally assigned to: @guilhermeblanco on GitHub. Jira issue originally created by user rdohms: I would like to propose a intermediary parent for the NoResult and NonUnique Exceptions, that is not as high level as ORMEXception, something in between. The reasoning for this is that sometime si want to get a single object out of the DB, and in case its not there i want to just get a null and carry on. For this I usually need to catch both exceptions as both results might trigger me to do something else, like abort. In some cases i do need to treat each of these in its own way, but in some cases it does not matter to which side the error went, it only matters that its not the expected SingleResult. Catching a ORMException is not adequate as it may include other error which would need to be treated differently. My proposal would be like: ORMException -> NotExpectedResultException -> {NoResult, NonUnique} Just a more detailed grouping of exceptions. Does this sound like something possible, or am I just nuts?

admin added the Improvement label 2026-01-22 13:47:33 +01:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: doctrine/archived-orm#2293