Releasing DB connections

2004-08-27 Thread Raphael . X . Mankin%GSK%SB
A bit of clarification please. One uses torque.getConnection to get a DB connection from the pool. How and when is it returned to the pool? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL

RE: CLOB vs BLOB

2004-08-27 Thread Thomas Fischer
Hi Sarav As I understand it, a BLOB is a binary large object, and a CLOB is a character large object. The difference between characters and bytes is the Character set, i.e. the mapping between a character and the byte sequence it represents. - With a blob, you have to use the right character

Antwort: Re: Antwort: AW: Disable Trigger in Torque?

2004-08-27 Thread arne . siegel
Henning P. Schmiedehausen wrote: Just use database name=apdcat defaultIdMethod=autoincrement No need for patches. Use the regular Torque distribution. Actually the dtd does not allow this: !ELEMENT database (external-schema*, domain*, table+) !ATTLIST database name CDATA #IMPLIED

Antwort: Releasing DB connections

2004-08-27 Thread Thomas Fischer
Hi, personally I use Transaction.begin() to get a connection and Transaction.commit(connection) , transaction.rollback(connection) or transaction.safeRollback(connection) to give it back to the pool. Thomas [EMAIL PROTECTED] schrieb am 27.08.2004 10:21:11: A bit of clarification

Re: Releasing DB connections

2004-08-27 Thread Raphael . X . Mankin%GSK%SB
Up to now I have assumed that things work as you explained. However opening new connections is typically a fairly slow business. When programming in C or Perl one gets used to using the same connection over and over again, processing transactions in a loop. This does not appear to be possible with

Re: Releasing DB connections

2004-08-27 Thread Thomas Fischer
[EMAIL PROTECTED] schrieb am 27.08.2004 12:58:15: Up to now I have assumed that things work as you explained. However opening new connections is typically a fairly slow business. Ok, but because of this, you use a connection pool. A pool keeps the connections open even if you do not use

AW: Antwort: Re: Antwort: AW: Disable Trigger in Torque?

2004-08-27 Thread Ferruh Zamangoer
First thank you for your replys. What I have read in Torque documentation is that the defaultIdMethod=autoincrement is deprecated, please use native?? When I'am using this IdMethod it could be that I become some problems in later versions of Torque or Regards Ferruh -Ursprungliche

RE: Putting schema into the select clause

2004-08-27 Thread mark.a.gold
Steve, This is an ongoing issue with Torque and one I have not seen a solution for. Although some solutions have been offered on this list there currently seems to be no practical way to fully qualify object names. -Original Message- From: Steve Toth [mailto:[EMAIL PROTECTED] Sent:

Re: Antwort: Re: Antwort: AW: Disable Trigger in Torque?

2004-08-27 Thread Henning P. Schmiedehausen
[EMAIL PROTECTED] writes: database name=apdcat defaultIdMethod=autoincrement No need for patches. Use the regular Torque distribution. Actually the dtd does not allow this: !ELEMENT database (external-schema*, domain*, table+) !ATTLIST database name CDATA #IMPLIED defaultIdMethod

Antwort: Re: Antwort: Re: Antwort: AW: Disable Trigger in Torque?

2004-08-27 Thread arne . siegel
Did you look at 3.1.1? I have here --- cut --- !ATTLIST database name CDATA #IMPLIED defaultIdMethod (idbroker|native|autoincrement|sequence|none) none defaultJavaType (object|primitive) primitive package CDATA #IMPLIED baseClass CDATA #IMPLIED basePeer CDATA #IMPLIED

Re: Releasing DB connections

2004-08-27 Thread Guy Galil
If you use Connection con = Torque.getConnection() to get the connection then you should use Torque.closeConnection(con) to close it: try { Connection con = Torque.getConnection(); /* use your connection here ... ...

Disable Trigger in Torque?

2004-08-27 Thread Ferruh Zamangoer
Hi, thanks again for any reply messages for my Problem. But I was little bit confused about the messages which settings I have to define in my schema.xml. The next step what I have done is to test every of your suggestions and I become the following results. First a cut of my database schema:

Re: Fwd: Putting schema into the select clause

2004-08-27 Thread Saravana Krishnan Kannan
Hi, I dont know much about the DBAdapter class, but can't you let the DBAdapter tell you whether SCHEMA.TABLE is allowed by the DB? That sounds like a nice generic way of doing it. -Sarav. -Original Message- From: Steve Toth [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Fri, 27 Aug

RE: Putting schema into the select clause

2004-08-27 Thread Lach, Thierry
1. Make sure the schema is optional. 2. Make sure that the schema can be overridden at runtime. We've got several schema that are identical and it would be nice to be able to do runtime selection of the schema (especially for reporting purposes) while using a single connection (alternative