You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a project with ZFDoctrine, I'm having a hard time using Behaviors that generate their own table/class (ex: log tables, versions, etc..): Doctrine_Record_Generator uses by default Doctrine_Import_Builder. As a result, the auto-generated auxiliary table created by the plugin do not respect ZFDoctrine's model naming conventions.
It would be interesting if we could create Template's plugins extending a ZFDoctrine_Record_Generator class that would override its method generateClass()
to use ZFDoctrine_Import_Builder instead of Doctrine_Import_Builder.
The text was updated successfully, but these errors were encountered:
obs: when extending the Record Generator, I had to use the following $options so I could have models compatible to those generated by ZFDoctrine's generate-models-from-yaml:
In a project with ZFDoctrine, I'm having a hard time using Behaviors that generate their own table/class (ex: log tables, versions, etc..): Doctrine_Record_Generator uses by default Doctrine_Import_Builder. As a result, the auto-generated auxiliary table created by the plugin do not respect ZFDoctrine's model naming conventions.
It would be interesting if we could create Template's plugins extending a ZFDoctrine_Record_Generator class that would override its method generateClass()
to use ZFDoctrine_Import_Builder instead of Doctrine_Import_Builder.
The text was updated successfully, but these errors were encountered: