Fix count method return value. #4.1#4069
Merged
taylorotwell merged 2 commits intolaravel:4.1from Apr 7, 2014
Andreyco:4.1
Merged
Fix count method return value. #4.1#4069taylorotwell merged 2 commits intolaravel:4.1from Andreyco:4.1
count method return value. #4.1#4069taylorotwell merged 2 commits intolaravel:4.1from
Andreyco:4.1
Conversation
Return number represented as integer instead of string.
Andreyco
changed the title
count method return value.count method return value. #4.1
Member
There was a problem hiding this comment.
Can you put a space in between the cast and the function call?
Contributor
Author
|
I did. |
taylorotwell
added a commit
that referenced
this pull request
Apr 7, 2014
Fix `count` method return value. #4.1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi there, I have very simple query
Actual output
Expected output
Happens on 4.1.x, but probably on 4.x versions as well.
Since this, we cannot relly on
===comparsion operator, which result intofalseall the time.Is this behaviour by design, or just a flaw?