Mailing-List: contact ibatis-user-java-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ibatis-user-java@incubator.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  b=yi85yc59vZwBRnQspPO6AcMOH6qXqIrztAlWdVJgoHZagt6TZ0sQFf/FmzcSE/APK1Unwo6UT1CclmmtP6/fBgPZ5iC0jSiqnQo1Y3VSn+KPFmnXzs8J2GYNbw6YFbSV8Mm61tEIb9kK6PZxLpdXWLXsPkt8yEGG8D2o6DfxHLc=
  ;
Message-ID: <20050316220435.14566.qmail@web50708.mail.yahoo.com>
Date: Wed, 16 Mar 2005 14:04:35 -0800 (PST)
From: Brett Gorres <bgorres@yahoo.com>
Reply-To: bgorres@yahoo.com
Subject: Re: Calling all ibatis + Derby / Cloudscape users [SOLVED]
To: ibatis-user-java@incubator.apache.org, cbegin@ibatis.com
In-Reply-To: 6667
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Thanks, Clinton for unit testing Derby + ibatis and
noting your successes here.  That was encouraging.

I learned today that I could alleviate my error by
prepending "APP." schema name to those problematic
table names in my SQL.  I will read up on that before
I using embedded Derby in another app.*  Otherwise,
everything went smoothly.

(I had sampled various eclipse db / derby plugins and
command-line SQL abilities when I created those
tables.)

Also, apparently in the SQL spec and various RDBMS
implementations, your schema names are sometimes
interpreted in case sensitive aNd/or case INsensitive
manner.  I didn't know that was so important.

*Meanwhile, my client has decided AGAINST using
Derby/Cloudscape in favor of Oracle 9i Lite for this
project.  Fair enough.  They have the licenses.

As for me, I will keep an eye on Derby; this was not a
bad intro all things considered.

And thanks to ibatis I won't dread swapping in
different databases.  Be agile.  Embrace change.

Later!

Regards,
-Brett

--- Clinton Begin <clinton.begin@gmail.com> wrote:
> I haven't experienced that problem.  I did switch to
> Derby for a while
> and ran all unit tests against it.  I only switched
> back because it
> wasn't as fast for unit tests as an in memory
> HSQLDB.  Other than
> that, it worked great.
> 
> Cheers,
> Clinton
> 
> 
> On Tue, 15 Mar 2005 11:09:48 -0800 (PST), Brett
> Gorres
> <bgorres@yahoo.com> wrote:
> > HI:
> > If anyone out there is even using ibatis with
> > driver=org.apache.derby.jdbc.EmbeddedDriver
> > 
> > You may be able to help me: (or I am just crazy!) 
> I
> > know there are some possible workarounds e.g.,
> hacking
> > SqlMapClientBuilder--but I'm trying to learn how
> to
> > get ibatis and derby going without resorting to
> that.
> > 
> > Here is the situation:
> > I have a small embedded Derby (/Cloudscape)
> database
> > in the same JVM as the application...
> > 
> > Ibatis has no trouble connecting to my tiny derby
> > testdb (created but not populated with anything),
> but
> > for some reason my other _populated_ database
> won't
> > start using the same code (after only changing the
> url
> > to my other database in database.properties).
> > 
> > <console-says>
> > "
> > Failed to start database
> > 'C:\work\projects\<<censored-actual-name>>', see
> the
> > next exception for details.
> > "
> > </console-says>
> > 
> > (fyi, there is no "next exception to look at from
> my
> > current vantage point...")
> > 
> > I know ibatis is just unhappy with the specific
> > database in question--not derby in
> general--because
> > when I change the url in database.properties to a
> > fictitious one, the error does change:
> > 
> > <console-says>
> > "
> > Database
> 'C:\work\projects\<<fictitious-name-here>>'
> > not found.
> > "
> > </console-says>
> > 
> > No angle brackets were actually used in my test.
> (In
> > case that is not clear.)
> > 
> > My questions:
> > 
> > 1) Has this ever happened to you?  Am I still on a
> > well-beaten path?
> > 
> > 2) Why does the small database work and the other
> > (still trivially small) other db NOT work?
> > 
> > Obviously there is something good about testdb and
> > something amiss with my other db.
> > 
> > If answer to 1 == No (otherwise I am just probably
> way
> > off), Is it possible that derby is is simply
> taking
> > too long to start up on my [trivially] larger db
> and
> > ibatis is therefore timing out?
> > 
> > p.s.
> > I've been using Oracle and MySQL with SQL Maps for
> a
> > long time and loving it!
> > 
> > Regards,
> > 
> > -Brett
> >
>