php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #77119 array_column has changed behaviour for classes
Submitted: 2018-11-08 01:47 UTC Modified: 2018-11-08 04:41 UTC
Votes:1
Avg. Score:3.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:1 (100.0%)
From: josh at engramdesign dot com dot au Assigned:
Status: Not a bug Package: Arrays related
PHP Version: 7.0.32 OS: Centos
Private report: No CVE-ID: None
View Add Comment Developer Edit
 [2018-11-08 01:47 UTC] josh at engramdesign dot com dot au 
Description:
------------
A recent update to 7.0.32 has caused this bug. Please refer to the reproducible example where an array of classes is supplied to `array_column`.

This worked fine in previous 7.0.x versions.

Test script:
---------------
$class = new \stdClass();
$class->name = 'Test';
var_dump($class);

$names = array_column([$class], 'name');
var_dump($names);

Expected result:
----------------
object(stdClass)#769 (1) { ["name"]=> string(4) "Test" }
array(0) { }

Actual result:
--------------
object(stdClass)#769 (1) { ["name"]=> string(4) "Test" }
array(1) { [0]=> string(4) "Test" }

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2018-11-08 02:02 UTC] peehaa@php.net 
> This worked fine in previous 7.0.x versions.

3v4l disagrees: https://3v4l.org/Nsjvl
 [2018-11-08 02:14 UTC] peehaa@php.net
-Status: Open +Status: Not a bug
 [2018-11-08 02:14 UTC] peehaa@php.net 
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php

In specific check the documentation of the function you are using including the possible changelog http://php.net/manual/en/function.array-column.php#refsect1-function.array-column-changelog
 [2018-11-08 02:32 UTC] josh at engramdesign dot com dot au 
Then why does the output for "Output for hhvm-3.17.3 - 3.22.0, 7.0.0 - 7.3.0rc4" show the following?

object(stdClass)#1 (1) {
  ["name"]=>
  string(4) "Test"
}
array(1) {
  [0]=>
  string(4) "Test"
}

I will note that 3v4l doesn't have 7.0.32 available to test, and it works as expected in 7.0.31.
 [2018-11-08 03:09 UTC] requinix@php.net 
Your expected behavior is incorrect. What the function is doing, and as you pointed out has been doing since 7.0.0, it was it should be doing: returning an array with the "name" properties extracted from the array of objects that was passed as the first argument.
 [2018-11-08 03:15 UTC] josh at engramdesign dot com dot au 
Well, I'm an idiot. The expected and actual results are around the wrong way. So sorry about that. I can't see anywhere to edit my original post either (sorry, not used to this bug tracker).

So what its returning is an empty array when it shouldn't be.

Does that make more sense now?
 [2018-11-08 04:41 UTC] requinix@php.net 
It's working for me...
 [2019-02-01 14:26 UTC] cravciucandy at gmail dot com 
The same problems are in PHP 7.0.33 built: Dec 11 2018 06:07:07
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Thu Apr 25 14:01:31 2024 UTC