Skip to content

Conversation

@daschl
Copy link
Contributor

@daschl daschl commented Jan 7, 2013

This changeset fixes and verifies that instead of null, false is returned
from the fetch method. This fixes a bug which causes CouchbaseCache not
to work in combination with the ORM library. Test added.

This changeset fixes and verifies that instead of null, false is returned
from the fetch method. This fixes a bug which causes CouchbaseCache not
to work in combination with the ORM library. Test added.
@doctrinebot
Copy link

Hello,

thank you for positing this Pull Request. I have automatically opened an issue on our Jira Bug Tracker for you with the details of this Pull-Request. See the Link:

http://doctrine-project.org/jira/browse/DCOM-158

Copy link
Member

Choose a reason for hiding this comment

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

opening { should be on the next line

Copy link
Member

Choose a reason for hiding this comment

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

Not only for couchbase?

This changeset makes sure that all supported caches return
false and not null when a key is not found. This ensures
compatibility with the ORM layer.
@daschl
Copy link
Contributor Author

daschl commented Jan 7, 2013

Okay, this also refactors the method one level up the tree so that it will be used for all caching adapters. I think this is necessary in order to make sure we don't break compatibility to the ORM layer which expects false and not null when no doc is found on fetch.

If possible, please merge since the CouchbaseCache doesn't work in combination with the ORM layer otherwise.

stof added a commit that referenced this pull request Jan 7, 2013
[Cache/CouchbaseCache] Return false instead of null for compat.
@stof stof merged commit c07ce5f into doctrine:master Jan 7, 2013
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.

5 participants