db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject Re: Schema does not exits exception
Date Wed, 29 Sep 2004 14:50:01 GMT
Hash: SHA1

Zahra Zahid wrote:

> Hi all,
>    This is the connection im using in my build.properties files....the
> database gets made but when some specific objects are 2 be loaded an
> exception is thrown:
> database=derby
> dbDialect=net.sf.hibernate.dialect.GenericDialect
> jdbcDriver=derby.jar
> dbURL=jdbc:derby:omar_registry;create=true;user=omar;password=omar
> dbUsername=omar
> dbPassword=omar
> jdbcClassName=org.apache.derby.jdbc.EmbeddedDriver
> dbLargeBinaryType=blob
> I need to know how to resolve this issue?

It's hard to see what is going on, namely what SQL statement is causing
the schema not found execption. But maybe an explanation will help.

The current schema for any connection defaults to a schema corresponding
to the user name, in this case OMAR. If no user name is supplied then
the user name (and hence current schema) defaults to APP.

However even though the current schema is set to the user name, that
schema may not exist. A schema is only created by CREATE SCHEMA or
creating an object (table etc.) in that schema (this is implicit schema
creation). Thus in your case the schema OMAR does not exist.

The one exception to this is the APP schema, which is always created,
though applications should not depend on that.

So you will see the schema not exists error if your application tries to
access the current schema before any objects have been created in it.
Possibilities are you try to perform a DROP TABLE before creating it, or
try to SELECT from a table to see if it should be created or not.

Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


View raw message