We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Actualy when I have defined some relation like:
$this->belongsTo( 'robots_id', 'Store\Toys\Robots', 'id', [ 'alias' => 'Robots', 'params' => [ 'columns' => 'id,name' ] ] );
And ask for
$model->getRobots()
in result I have two columns id and name, and its expected result.
But if i as for:
$model->getRobots(['columns'=>'id,price,name'])
in result I have again two columns without price.
I think that is a bug in https://github.com/phalcon/cphalcon/blob/master/phalcon/mvc/model/manager.zep#L1307
let builder = this->createBuilder(this->_mergeFindParameters(extraParameters, parameters));
we are overwriting relation parameters on provided parameters... It's suprising that in https://github.com/phalcon/cphalcon/blob/master/phalcon/mvc/model/manager.zep#L1364 it''s reverse logic.
The text was updated successfully, but these errors were encountered:
Fixed in the 3.2.x branch. Feel free to open a new issue if the problem appears again. Thank you for contributing.
3.2.x
Sorry, something went wrong.
sergeyklay
No branches or pull requests
Expected and Actual Behavior
Actualy when I have defined some relation like:
And ask for
in result I have two columns id and name, and its expected result.
But if i as for:
in result I have again two columns without price.
I think that is a bug in https://github.com/phalcon/cphalcon/blob/master/phalcon/mvc/model/manager.zep#L1307
we are overwriting relation parameters on provided parameters...
It's suprising that in https://github.com/phalcon/cphalcon/blob/master/phalcon/mvc/model/manager.zep#L1364 it''s reverse logic.
Details
--
Przemek
The text was updated successfully, but these errors were encountered: