I'm not aware of an advantage, and from what I know Doctrine2 does
away with that.
Daniel
On Jul 4, 9:37 am, Javier Garcia wrote:
> On 07/04/2010 11:44 AM, G bor F si wrote:
>
>
>
> > The question is doctrine-related, not propel. Doctrine indeed uses
> > magic methods instead of generating the
On 07/04/2010 11:44 AM, Gábor Fási wrote:
The question is doctrine-related, not propel. Doctrine indeed uses
magic methods instead of generating them.
On Sat, Jul 3, 2010 at 14:58, rumianom wrote:
What do you mean "on the air"?
Set/get methods are generated in base model classes and you ca
The question is doctrine-related, not propel. Doctrine indeed uses
magic methods instead of generating them.
On Sat, Jul 3, 2010 at 14:58, rumianom wrote:
> What do you mean "on the air"?
> Set/get methods are generated in base model classes and you can
> override them in your model class ( OOP )
What do you mean "on the air"?
Set/get methods are generated in base model classes and you can
override them in your model class ( OOP ).
When you build-model, base model is generated once more time but your
model classes remain untouched.
>From my knowledge of Propel.
On 2 Lip, 17:51, Javier Garc
Because you can have this "on the air" get/set methods in the parent
class and you don't have to generate all get/set methods in your
concrete model.
On 1 čnc, 18:59, Javier Garcia wrote:
> Hi,
>
> why the get and set methods of the model classes are created "on the
> air", instead of generate t
