> One question, the "tasks" part of torque uses your "build.properties" info to
> connect to
> the server. Are you changing the values here or in the Torque.properties
> file, which
> only effects the runtime?
Actually I changed the build-torque.xml to use a config.properties. Which
contains e
> Did you try to use the configured schema name instead of "%" ?
> Maybe a case sensitivity issue ?
I'll check that tomorrow.
smime.p7s
Description: S/MIME cryptographic signature
Hi, Thomas,
> Could you please open a jira issue for this ?
https://issues.apache.org/jira/browse/TORQUE-112
Peace,
--Carl
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hmm, this is interesting. FWIW, I believe that the test-project
contains a test for the jdbc task. I ran the test suite using the
3.3-RC3 candidate against a MS SQL Server 2000 install with the
jTDS driver and it passed. But I'm not a 100% sure that the jdbc
task is part of that.
Also, I just
Hi, Thomas,
> - Unfortunately, select and delete sql is composed
> differently. Have you tried to debug the sql code which is
> used for the delete ?
I've now had a chance to debug with the torque source, and here is my
best explanation of what is going on. There doesn't appear to be any
sql c
Manaster, Carl wrote:
Below my signature is a test that demonstrates the problem I'm seeing.
We're using torque 3.3. When I try to delete through a join, it is
deleting all records from the table, instead of just the records of
interest. It does not matter whether records in the T1 table exist
Hi, Thomas,
> Could you please open a jira issue for this ?
Could you send me a link with jira instructions, please? I don't know
jira. Thanks.
Peace,
--Carl
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional command
> > - A criteria can be changed when a select is made. You use
> > the same criteria to count and to delete. This is typically
> > not a good idea.
>
> That comes as a surprise to me - I would not expect use of a criteria to
> change it. I tried it just now with separate but (initially) identical
Could you please open a jira issue for this ?
Thanks,
Thomas
"Manaster, Carl" <[EMAIL PROTECTED]> schrieb am 10.04.2008 17:55:22:
> Hi, all,
>
> Here's an updated test case that eliminates the criteria re-use issue
> and demonstrates that the delete has the desired behavior when no
Did you try to use the configured schema name instead of "%" ? Maybe a case
sensitivity issue ?
Sorry, just wild guesses,
Thomas
Thoralf Rickert <[EMAIL PROTECTED]> schrieb am 10.04.2008 18:05:45:
> > What Torque does is it opens a connection to the db, goes for
> > the metadata of
> What Torque does is it opens a connection to the db, goes for
> the metadata of the connection and makes the call
>
> tableNames = dbMeta.getTables(null, dbSchema, "%", types);
>
> Maybe you can try to do this manually and play around to see
> what goes wrong ?
>
> It may also be that you have a
Hi, all,
Here's an updated test case that eliminates the criteria re-use issue
and demonstrates that the delete has the desired behavior when no join
is used.
Peace,
--Carl
package com.activx.apps.ms.quan.util.tests;
import org.apache.torque.TorqueException;
import org.apache.torque.util.CountH
What Torque does is it opens a connection to the db, goes for the metadata
of the connection and makes the call
tableNames = dbMeta.getTables(null, dbSchema, "%", types);
Maybe you can try to do this manually and play around to see what goes
wrong ?
It may also be that you have a permission pro
Hi, Thomas,
Thank you for the reply.
> - A criteria can be changed when a select is made. You use
> the same criteria to count and to delete. This is typically
> not a good idea.
That comes as a surprise to me - I would not expect use of a criteria to
change it. I tried it just now with separ
Hi all,
I try to extract a database schema from a SQL Server 2005. I tried both drivers
jTDS and the Microsoft JDBC Driver 1.2. In both versions I can access the
database, but the resulting XML schema for Torque is empty.
When I run the JDBC task in build-torque.xml (fresh 3.3) I got this conso
Two things come to my mind
- A criteria can be changed when a select is made. You use the same
criteria to count and to delete. This is typically not a good idea.
- Unfortunately, select and delete sql is composed differently. Have you
tried to debug the sql code which is used for the delete ?
Hello all,
today I will unsubscribe from the Torque mailing list and wish to say
goodbye and thank you for the help many of you provided!
Things evolve, and by now we are dealing with other persistence
frameworks - not always as joyful as I exect... ;-)
Keep up the good work, and thank you again
17 matches
Mail list logo
