In my opinion this is one of the main disadvantages of doctrine, but compared to propel you will have to decide for yourself if you can accept this drawback with all doctrine features in mind that propel is not shipped with.
Ok, man could enrich the generated classes' code with code-completing php-doc comments. But this would not solve every aspect of the problem, because in doctrine's case every property is determined by so to say class introspection. There is no method - beeing it a getter or a setter or simply a class property - that is physically declared in your model classes - as propel does it with the means of code generation (propel-gen). In doctrine, all method calls are mapped by php's magic methods to internally nested parameter holders. So you'll probably have to live with that. On 8 Jul., 13:34, Stefan Sturm <[email protected]> wrote: > Hello, > > I found this in the forums, but it is not working with > 1.2...http://forum.symfony-project.org/index.php/m/81335/#msg_81335 > > Greetings, > Stefan Sturm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
