[FLOW3-general] Different Databases for Different Packages
Thomas Rödiger
tom at datenarbeit.de
Mon Jan 16 17:41:35 CET 2012
Hi there,
I have read that the configuration is read in the order
package-configuration, global configuration, app-context. So every
package could be configured with it's own database. Theoreticaly. In my
case, I use the flow3-authorization, and a package I have wrote. The
database is defined in app-context. Now i want a new package, that
accesses another database. According to the loading order of
configuration i now had got to configure the database in the packages,
including the Flow3-Package, where i had to fill in my data in the
default-configuration, which is not very safe wenn running updates.
Additionaly I will loose my Appcontext (no dev an production-context
anymore). Is the another way to configure a separate database for a
single package? The way I discribed seems not to be very handy.
One additional question. The database I want to connect is an existing
database. i don't want doctrine to change the structure of the database
when running "doctrine:update". Is that possible? I found that doctrine
has an reverse-engineering-tool to create yaml-configs from existing
databases
(http://www.doctrine-project.org/docs/orm/2.1/en/reference/tools.html#reverse-engineering).
Could this be a solution and is it integratible to flow3?
Thanks in advance,
thomas
More information about the FLOW3-general
mailing list