Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Users List" <torque-user@db.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of Greg.Monroe@dukece.com
 designates 65.112.55.73 as permitted sender)
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: using a second database
Date: Fri, 14 Apr 2006 10:17:43 -0400
Message-ID: <8F5843B903F59D4C8C6806BB49A39119062A48@dukece-mail3.dukece.com>
Thread-Topic: using a second database
Thread-Index: AcZfxA9C5HdN5Dp/SWa/KqYAWdYYgwAB2qcg
From: "Greg Monroe" <Greg.Monroe@DukeCE.com>
To: "Apache Torque Users List" <torque-user@db.apache.org>

One additional thought here.  There is a Torque.init(Configuration)=20
method that can be used instead of Torque.init(fileName).  You=20
could build your own commons Configuration object from Turbine's=20
properties to match your needs.

> -----Original Message-----
> From: Helge Weissig [mailto:helgew@grajagan.org]=20
>=20
> The requirement to have the name in the schema and in the =20
> configuration match is somewhat cumbersome for a multi-developer =20
> environment, where each developer needs to have their own database. =20
> The old way (way old!!) used to be that the db name was only =20
> specified once in TurbineResources.properties and hence needed to be =20
> changed only once when setting up a new sandbox. Maybe it's easier =20
> when using the Turbine M.E.T.A approach... does anyone know?
>=20
> As for using the Peers in the oracle db, we don't have any. The =20
> database is a commercial one and we only use very few tables=20
> from it. =20
> Since learning about the jdbc2xml capabilities of Torque, I have =20
> considered generating the peers for those.
>=20

Duke CE Privacy Statement
Please be advised that this e-mail and any files transmitted with it are =
confidential communication or may otherwise be privileged or =
confidential and are intended solely for the individual or entity to =
whom they are addressed.  If you are not the intended recipient you may =
not rely on the contents of this email or any attachments, and we ask =
that you  please not read, copy or retransmit this communication, but =
reply to the sender and destroy the email, its contents, and all copies =
thereof immediately.  Any unauthorized dissemination, distribution or =
copying of this communication is strictly prohibited.


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org