The example in the docs shows $this->mapValue() being called in setTableDefinition(), but that doesn't work. It needs to be called in construct() for it to work correctly.
Having said that, I think this is the wrong approach. Doesn't it make more sense to define a custom property in setTableDefinition(), alongside all of the regular columns?
> The example in the docs shows $this->mapValue() being called in
> setTableDefinition(), but that doesn’t work. It needs to be called in
> construct() for it to work correctly.
> Having said that, I think this is the wrong approach. Doesn’t it make more
> sense to define a custom property in setTableDefinition(), alongside all of
> the regular columns?
> Thanks,
> Adam
-- Jonathan H. Wage (+1 415 992 5468)
Open Source Software Developer & Evangelist
sensiolabs.com | jwage.com | doctrine-project.org | symfony-project.org
You can contact Jonathan about Doctrine, Symfony and Open-Source or for
training, consulting, application development, or business related questions
at jonathan.w...@sensio.com
From: doctrine-dev@googlegroups.com [mailto:doctrine-dev@googlegroups.com]
On Behalf Of Jonathan Wage
Sent: Thursday, June 25, 2009 8:53 AM
To: doctrine-dev@googlegroups.com
Subject: [doctrine-dev] Re: mapValue - documentation incorrect
The example in the docs shows $this->mapValue() being called in
setTableDefinition(), but that doesn't work. It needs to be called in
construct() for it to work correctly.
Having said that, I think this is the wrong approach. Doesn't it make more
sense to define a custom property in setTableDefinition(), alongside all
of the regular columns?
Thanks,
Adam
-- Jonathan H. Wage (+1 415 992 5468)
Open Source Software Developer & Evangelist
sensiolabs.com | jwage.com | doctrine-project.org | symfony-project.org
You can contact Jonathan about Doctrine, Symfony and Open-Source or for
training, consulting, application development, or business related
questions at jonathan.w...@sensio.com
> The example in the docs shows $this->mapValue() being called in
> setTableDefinition(), but that doesn’t work. It needs to be called in
> construct() for it to work correctly.
> Having said that, I think this is the wrong approach. Doesn’t it make more
> sense to define a custom property in setTableDefinition(), alongside all of
> the regular columns?
> Thanks,
> Adam
> --
> Jonathan H. Wage (+1 415 992 5468)
> Open Source Software Developer & Evangelist
> sensiolabs.com | jwage.com | doctrine-project.org | symfony-project.org
> You can contact Jonathan about Doctrine, Symfony and Open-Source or for
> training, consulting, application development, or business related questions
> at jonathan.w...@sensio.com
-- Jonathan H. Wage (+1 415 992 5468)
Open Source Software Developer & Evangelist
sensiolabs.com | jwage.com | doctrine-project.org | symfony-project.org
You can contact Jonathan about Doctrine, Symfony and Open-Source or for
training, consulting, application development, or business related questions
at jonathan.w...@sensio.com
|
