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
I'm developing a bundle that gives access to some models which should be persisted differently depending on how my bundle is configured. For instance, models in my bundle can conditionally have an i18n behaviour attached if it's needed by the bundle user (that's just a single usecase, there are more as it seems to me).
So, basically I need to be able to conditionally load different schema files during container compilation.
I've stumbled upon schema.xml filename being hardcoded in Propel\PropelBundle\Command\AbstractCommand::getSchemasFromBundle, and could not find it anywhere else, not as a container parameter default value nor anything else. Does that mean that conditionally loading schemas is not possible?
If that's true, then my proposal is to let PropelBundle users define schemas Propel should use in their DependencyInjection\Extension child classes' ::load method.
The text was updated successfully, but these errors were encountered:
I'm facing very similar problem: I need to let application load partial schema with user tables optionally where database name will differs from the rest of the schemas.
Could I solve this other way? Eg: by overriding DATABASE_NAME in peer classes? Schema loading seems to me as much cleaner approach.
I'm developing a bundle that gives access to some models which should be persisted differently depending on how my bundle is configured. For instance, models in my bundle can conditionally have an
i18n
behaviour attached if it's needed by the bundle user (that's just a single usecase, there are more as it seems to me).So, basically I need to be able to conditionally load different schema files during container compilation.
I've stumbled upon
schema.xml
filename being hardcoded inPropel\PropelBundle\Command\AbstractCommand::getSchemasFromBundle
, and could not find it anywhere else, not as a container parameter default value nor anything else. Does that mean that conditionally loading schemas is not possible?If that's true, then my proposal is to let
PropelBundle
users define schemas Propel should use in theirDependencyInjection\Extension
child classes'::load
method.The text was updated successfully, but these errors were encountered: