he folks, im playing around with propel1.5 and the new features.
i ran into 2 strange behaviors: here is my simple schema first: propel: garden: id: name: { type: varchar(255) } plant: _attributes: { abstract: true } id: common_name: { type: varchar(255) } latin_name: { type: varchar(255) } garden_id: { type: integer, foreign_table: garden, foreign_reference: id} flower: _propel_behaviors: concrete_inheritance: extends: plant copy_data_to_parent: false bloom_color: { type: varchar(255) } tree: _propel_behaviors: concrete_inheritance: extends: plant copy_data_to_parent: false height: {type: integer } i think you get it, whe have an abstract plant, from which flower and tree extends. so here are my 2 strange behaviors: 1. a table is generated for plant (its abstract, so i dont need a table?!) 2. while building i get a "fatal error" saying: Fatal error: Class PlantPeer contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (BasePlantPeer::getOMClass) in /PATH/TO/PROJECT/lib/model/ PlantPeer.php on line 19 so why is a nonabstract method generated into a abstract basefile? is it a bug or a feature or am i missing something important? issue 1. can be resolved be deleting the obsolete table directly in the database issue 2. can be resolved by adding the getOMClass to the generated Peer Class, or by declaring this class abstract cheerz robert please help... -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en