db-torque-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Evguenia Krylova" <evguenia.kryl...@doit.wisc.edu>
Subject Re: Torque conn pooling - second db?
Date Tue, 10 Dec 2002 17:32:25 GMT
I think this will work for you:

Connection con = null;
try
{
con = Transaction.begin(dbName);
// do you work
Transaction.commit(con);
}
catch(TorqueException e)
{
Transaction.safeRollback(con);
throw e;
}

Ev

----- Original Message -----
From: <JDiggans@genelogic.com>
To: "Turbine Torque Users List" <turbine-torque-user@jakarta.apache.org>
Sent: Monday, December 09, 2002 4:43 PM
Subject: Torque conn pooling - second db?


>
> Hello all, is there a way to have Torque pool and manage connections to a
> second schema that's not in an O/R model and has a different login/pw/sid?
> Ideally I'm just looking for something lazy like:
>
> Connection myConn = Torque.getConn('db2name');
>
> but I imagine life is rarely that easy ...
> -j
>
> -------------------------------------------------
> James Diggans
> Bioinformatics Programmer
> Gene Logic, Inc.
> Phone: 301.987.1756
> FAX: 301.987.1701
>
>
>
>
> --
> To unsubscribe, e-mail:
<mailto:turbine-torque-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
<mailto:turbine-torque-user-help@jakarta.apache.org>
>
>


Mime
View raw message