You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-user@db.apache.org by Tomáš Procházka <t....@centrum.cz> on 2006/04/16 15:45:44 UTC
Torque and iBATIS
Hi.
I have two questions.
For what is Torque better and for what iBATIS? Why Apache has two similar projects?
And why Torque use this:
xercesImpl-2.6.2.jar
xml-apis-2.0.2.jar
I this need in Java 1.5? A try delete it and all works.
Thanks you.
--
Tomas Prochazka
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org
Re: Torque and iBATIS
Posted by Tomáš Procházka <t....@centrum.cz>.
Hi.
I have again small question.
Why you prefer Torque before Hibernate?
-------------------------- Original message --------------------------
From: Thomas Fischer <tf...@apache.org>
Subject: Torque and iBATIS
Date: Sunday, April 16, 2006, 7:31:29 PM
Attachments: Část.txt
msgid:20060416101514.A20443@minotaur.apache.org
T> I'm not an iBATIS user, but from a brief glance, Torque needs minimal
T> preparation to get a working database model. The database objects, sql
T> scripts, data accessors are all generated. In contrast to that, iBATIS
T> seems to force you to write your own SQL for everything you do. This is
T> cumbersome for simple statements, but very powerful for complicated sql.
T> So my personal advice would be : If you use simple SQL, use Torque, if you
T> use complicated and involved SQL, use iBATIS.
T> It is also a matter of personal taste in the end.
----------------------- End of original message ----------------------
--
Tomas Prochazka
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org
Re: Torque and iBATIS
Posted by Thomas Fischer <tf...@apache.org>.
On Sun, 16 Apr 2006, TomṠProch�zka wrote:
>
> But in Torque I can also use my own SQL, whne I need some complication operation.
> For example: BazarsPeer.executeQuery("SELECT ...");
Yes, but the results of that query are not automatically mapped to java
objects. You can do custom sql in Torque, but it is not very convenient.
> I don't found any information about speed of Torque.
Nobody has yet cared to benchmark it. For the usual stuff (simple
selects, updates etc ), the speed of the OM layer is not
important as the database is the bottleneck in my experience. I'd guess
that Torque is not slow there, because it does not need reflection.
A known weakness of the speed of Torque is mass updates and mass deletes.
Torque loads all datasest instead of issuing a simple sql statement.
Thomas
Re: Torque and iBATIS
Posted by Tomáš Procházka <t....@centrum.cz>.
Hi.
Thanks you for reply.
T> I'm not an iBATIS user, but from a brief glance, Torque needs minimal
T> preparation to get a working database model. The database objects, sql
T> scripts, data accessors are all generated. In contrast to that, iBATIS
T> seems to force you to write your own SQL for everything you do. This is
T> cumbersome for simple statements, but very powerful for complicated sql.
T> So my personal advice would be : If you use simple SQL, use Torque, if you
T> use complicated and involved SQL, use iBATIS.
T> It is also a matter of personal taste in the end.
But in Torque I can also use my own SQL, whne I need some complication operation.
For example: BazarsPeer.executeQuery("SELECT ...");
I don't found any information about speed of Torque.
T> Torque's runtime runs on java 1.3, 1.4 and 1.5, and the generator runs
T> on 1.4 and 1.5. To achieve this downward compatibilty, some libraries are
T> included which may not be needed in java 1.5. I have never tried to find
T> out the minimal set of libraries needed to run torque in 1.5, so no idea
T> whether these special libraries are needed or not in 1.5. As long as you
T> do not get a ClassDefNotFoundError, you're fine.
Project size is important for me ;-)
-------------------------- Original message --------------------------
From: Thomas Fischer <tf...@apache.org>
Subject: Torque and iBATIS
Date: Sunday, April 16, 2006, 7:31:29 PM
Attachments: Část.txt
msgid:20060416101514.A20443@minotaur.apache.org
T> On Sun, 16 Apr 2006, Tomáą Procházka wrote:
>> Hi.
>> I have two questions.
>> For what is Torque better and for what iBATIS?
>> Why Apache has two similar projects?
T> There is no Master Plan of open source software in general or at the ASF.
T> There are even two other ORM projects at the ASF, cayenne (in incubation)
T> and OJB.
>> And why Torque use this:
>> xercesImpl-2.6.2.jar
>> xml-apis-2.0.2.jar
>> I this need in Java 1.5? A try delete it and all works.
T> Thomas
----------------------- End of original message ----------------------
--
Tomas Prochazka
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org
Re: Torque and iBATIS
Posted by Thomas Fischer <tf...@apache.org>.
On Sun, 16 Apr 2006, TomṠProch�zka wrote:
> Hi.
>
> I have two questions.
>
> For what is Torque better and for what iBATIS?
I'm not an iBATIS user, but from a brief glance, Torque needs minimal
preparation to get a working database model. The database objects, sql
scripts, data accessors are all generated. In contrast to that, iBATIS
seems to force you to write your own SQL for everything you do. This is
cumbersome for simple statements, but very powerful for complicated sql.
So my personal advice would be : If you use simple SQL, use Torque, if you
use complicated and involved SQL, use iBATIS.
It is also a matter of personal taste in the end.
> Why Apache has two similar projects?
There is no Master Plan of open source software in general or at the ASF.
There are even two other ORM projects at the ASF, cayenne (in incubation)
and OJB.
>
> And why Torque use this:
> xercesImpl-2.6.2.jar
> xml-apis-2.0.2.jar
>
> I this need in Java 1.5? A try delete it and all works.
Torque's runtime runs on java 1.3, 1.4 and 1.5, and the generator runs
on 1.4 and 1.5. To achieve this downward compatibilty, some libraries are
included which may not be needed in java 1.5. I have never tried to find
out the minimal set of libraries needed to run torque in 1.5, so no idea
whether these special libraries are needed or not in 1.5. As long as you
do not get a ClassDefNotFoundError, you're fine.
Thomas