#1208: ability to define record level handlers for custom fields
-----------------------------------+--------------------------------------- -
 Reporter:  ccunningham            |       Owner:  romanb
     Type:  defect                 |      Status:  new  
 Priority:  minor                  |   Milestone:        
Component:  Listeners              |     Version:  0.11  
 Keywords:                         |    Has_test:  0    
 Mystatus:  Pending Core Response  |   Has_patch:  0    
-----------------------------------+--------------------------------------- -
 It would be nice if you could put the equivalent of a preHydrate handler
 in your record class to add custom/calculated fields to your model. The
 current method requires a HydrateListener which works, but requires you to
 either have one for each type of custom field you want, or just one that
 has to do some introspection and switches to handle different things. If
 you have a dozen models each of which may need their own set of custom
 fields, this becomes a real pain. If you could just throw it in the record
 class like:

 public function preHydrate( $event )
 {

   if ( $this->due_date < ... )
   {
     $this->status = 'current';
   }
   else
   {
     $this->status = 'expired';
   }
 }

--
Ticket URL: <http://trac.phpdoctrine.org/ticket/1208>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper

#1208: ability to define record level handlers for custom fields
--------------------------+------------------------------------------------ -
  Reporter:  ccunningham  |       Owner:  romanb              
      Type:  defect       |      Status:  closed              
  Priority:  minor        |   Milestone:                      
 Component:  Listeners    |     Version:  0.11                
Resolution:  invalid      |    Keywords:                      
  Has_test:  0            |    Mystatus:  Pending Core Response
 Has_patch:  0            |  
--------------------------+------------------------------------------------ -
Changes (by guilhermeblanco):

  * status:  new => closed
  * resolution:  => invalid

Comment:

 You can do it through postHydrate listener and access the element through
 $event->data.

 Marking the ticket as invalid. If it's not the case, reopen the ticket
 with a test case of expected behavior.

--
Ticket URL: <http://trac.phpdoctrine.org/ticket/1208#comment:1>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper

#1208: ability to define record level handlers for custom fields
--------------------------+------------------------------------------------ -
  Reporter:  ccunningham  |       Owner:  romanb              
      Type:  defect       |      Status:  closed              
  Priority:  minor        |   Milestone:  1.0.0-BETA1          
 Component:  Listeners    |     Version:  0.11                
Resolution:  invalid      |    Keywords:                      
  Has_test:  0            |    Mystatus:  Pending Core Response
 Has_patch:  0            |  
--------------------------+------------------------------------------------ -
Changes (by romanb):

  * milestone:  => 1.0.0-BETA1

--
Ticket URL: <http://trac.phpdoctrine.org/ticket/1208#comment:2>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper

#1208: ability to define record level handlers for custom fields
--------------------------+------------------------------------------------ -
  Reporter:  ccunningham  |       Owner:  romanb              
      Type:  defect       |      Status:  reopened            
  Priority:  minor        |   Milestone:  1.0.0-BETA1          
 Component:  Listeners    |     Version:  0.11                
Resolution:               |    Keywords:                      
  Has_test:  0            |    Mystatus:  Pending Core Response
 Has_patch:  0            |  
--------------------------+------------------------------------------------ -
Changes (by ccunningham):

  * status:  closed => reopened
  * resolution:  invalid =>

Comment:

 Yes, it can be done, however it's a real pain.

 I have a number of classes I want to do this on. I have a few entity
 classes representing people, I have some other classes which need a piece
 of data for 'name' where it's based on whether a custom name has been
 chosen, etc. It can be done through the listener interface, however that
 would involve having one listener class with a big switch statement ( to
 perform the desired custom field for each model type ) or create a bunch
 of different listener classes and assign them on a per table basis.
 Essentially I either have one big ugly global listener that isn't needed
 on all objects, or a bunch of small simple ones I have to attach on each
 model type.

 While that does do what I want, it isn't convenient or simple...

 Why can't I just put a postHydrate() function in each model class and do
 what I want there? It would greatly simplify the process and let you keep
 these little snippets nicely nested in their own models, so instead of
 having all these listener classes laying around I have a nice clean model.

--
Ticket URL: <http://trac.phpdoctrine.org/ticket/1208#comment:3>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper

#1208: ability to define record level handlers for custom fields
--------------------------+------------------------------------------------ -
  Reporter:  ccunningham  |       Owner:  romanb              
      Type:  defect       |      Status:  reopened            
  Priority:  minor        |   Milestone:  1.1.0                
 Component:  Listeners    |     Version:  1.0                  
Resolution:               |    Keywords:                      
  Has_test:  0            |    Mystatus:  Pending Core Response
 Has_patch:  0            |  
--------------------------+------------------------------------------------ -
Changes (by jwage):

  * version:  0.11 => 1.0
  * milestone:  Unknown => 1.1.0

--
Ticket URL: <http://trac.doctrine-project.org/ticket/1208#comment:4>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper