criteria constructor, e.g. new Criteria(defaultDB).
This will make sure that the name used will match the schema name.
-Original Message-
From: Sheldon Ross [mailto:sr...@simmgene.com]
Sent: Monday, November 16, 2009 5:19 PM
To: Apache Torque Users List
Subject: Re: Criteria needs write
Greg Monroe wrote:
Connection srcConn = Torque.getConnection(databaseA);
Connection destConn = Torque.getConnection(databaseB);
Don't want to be picky, but the recommended method is
Connection srcConn = Transaction.begin(databaseA);
} finally {
Torque.closeConnection(srcConn);
List
Subject: Re: Criteria needs write permissions?
Does that mean that a Torque object can be used with two different
connections as long as no pool is involved?
From: Thomas Vandahl t...@apache.org
To: torque-user@db.apache.org
Sent: Fri, November 13
needs write permissions?
Does that mean that a Torque object can be used with two different
connections as long as no pool is involved?
From: Thomas Vandahl t...@apache.org
To: torque-user@db.apache.org
Sent: Fri, November 13, 2009 1:27:26 PM
Subject: Re: Criteria
On 13.11.09 08:12, Thomas Fischer wrote:
I'm not sure whether this is a bug or not, I need to think about it. If i
remember correctly, the database name is used for the database connection
(including credentials) and the table layout. Probably there are some cases
where this wants to be
Does that mean that a Torque object can be used with two different connections
as long as no pool is involved?
From: Thomas Vandahl t...@apache.org
To: torque-user@db.apache.org
Sent: Fri, November 13, 2009 1:27:26 PM
Subject: Re: Criteria needs write
The why is a good question, the table is not found. The tables hashmap
in the dbMap appears to be empty.
It of course is found when using the other db connection. It looks like
I'm gonna have to dig for awhile.
Thanks.
Thomas Fischer wrote:
The null ointer exception seems to come from
. This is because it provided a known class
that knows (via extension) the user settable om package.
-Original Message-
From: Sheldon Ross [mailto:sr...@simmgene.com]
Sent: Thursday, November 12, 2009 3:25 PM
To: Apache Torque Users List
Subject: Re: Criteria needs write permissions?
The why
it provided a known class
that knows (via extension) the user settable om package.
-Original Message-
From: Sheldon Ross [mailto:sr...@simmgene.com]
Sent: Thursday, November 12, 2009 3:25 PM
To: Apache Torque Users List
Subject: Re: Criteria needs write permissions?
The why is a good question
:28 PM
To: Apache Torque Users List
Subject: Re: Criteria needs write permissions?
Ok, I think this maybe a bug. After watching the addTable method in
DatabaseMap, It appears to add the table to the default database dbMap
even if the criteria is querying against a different database
Ok, I apologize for the traffic.
No reason to apologize for anything. This is a perfectly valid question.
Here goes, when you build the database objects, it hardcodes in the
database name that exists in your schema.xml. The code is in the
doBuild() method of the ${Table}MapBuild.java
The null ointer exception seems to come from reading the table or column
map. Can you put a breakpoint in SQLBuilder.java:497 and see whether the
table or the column cannot be found (and why it is not found)?
Thomas
Ok so I was trying to make our site a little safer from sql injections,
so
12 matches
Mail list logo
