Login | Register
My pages Projects Community openCollabNet

Reply to message

* = Required fields
* Subject
* Body
Send reply to
Author (directly in email)
Please type the letters in the image above.

Original message

Author hlellelid
Full name Hans Lellelid
Date 2007-04-03 15:52:30 PDT
Message Robert Bruce wrote:
> I want to reuse the generated classes for multiple databases, so
> effectively they exist as part of a shared library for instances of my
> application. However because the DATABASE_NAME constant in the Peer
> classes is set to the name of the database against which they were
> originally built, I can't (to my knowledge) dynamically use a different
> database.

Well, you effectively can change your database at runtime. The
DATABASE_NAME constant is simply an identifier that tells Propel "use
the connection info associated with that key in the configuration file".
  The DATABASE_NAME need have no actual relationship with the actual
name of your database in your RDBMS.

To change a database name (or any other properties of the connection) at
runtime you can use the Propel::setConnection() (I think that's a valid
method...) or setConfiguration().

Does that help?