Mailing-List: contact ibatis-user-java-help@incubator.apache.org; run by ezmlm
Received-SPF: pass (hermes.apache.org: domain of oliver.zeigermann@gmail.com
 designates 64.233.184.195 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=X16KKwosSCWwdGuC8/am9j9j8NtMykL8sZiEykzeHa9dahgYbzvSYimjBLHCIgk4uKJKGSeQHFYydv50zMpI36MF1FMHuetu0VUpXO6syuohRcsfnmTwGrVB0wbVq8ucsAnp6NtsniaOrZthQNs60hI/KBdQ/IVylVcTVv/m5/0=
Message-ID: <9da4f45204112913405395fe91@mail.gmail.com>
Date: Mon, 29 Nov 2004 22:40:04 +0100
From: Oliver Zeigermann <oliver.zeigermann@gmail.com>
Reply-To: ozeigermann@apache.org
To: ibatis-user-java@incubator.apache.org
Subject: Re: A few dumb questions
In-Reply-To: <s1aaff88.072@cfo-msg.plumcreek.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <s1aaff88.072@cfo-msg.plumcreek.net>

Hi Brandon,

thanks for your answers, more questions inline ;)


On Mon, 29 Nov 2004 10:52:48 -0700, Brandon Goodin
<brandon.goodin@plumcreek.com> wrote:
>  
> 
> >1) which databases are known to work with ibatis? Really all known
> >ones? Or this there an explicite list? 
>   
> any database that has a jdbc driver that is spec compliant 

Having read a number of answers I now think I understand. I write the
SQL, so I am responsible for the dialect and thus ibatis works for all
dbs, right?

If so is there any support for me supporting a number of databases? I
nice way to handle different dialects?

> >2) how ibatis compares to OBJ (http://db.apache.org/ojb) or hibernate?
> >What would be reasons for ibatis? 
>   
> Hibernate and OJB are ORM tools. IBatis is a SQL Mapping tool. You would use
> IBatis because it's functionality is much easier to grasp and it serves a
> clear concise purpose and sheds the uneeded complexities of ORM. It doesn't
> seek to be the Uber tool. I like our tagline "JDBC made easy". 

I see. How does it relate to 

http://jakarta.apache.org/commons/dbutils/

then?

> Caching and dirty checking work fine when you have a database whose content
> is only altered through a single application. If there are any other changes
> that will be happening to the database then you will run into stale data
> issues. My recommendation is to only cache data that is rarely changed and
> not volatile. 

I understand this is true for caching. I thought dirty checking
usually is done inside a transaction where I can be pretty sure the
data I have just read has not been changed in the meantime. Am I
wrong?

Thanks again,

Oliver