Hi Gul,
Derby automatically uses the username as a schema name. A quick look
through the derby documentation found this :
http://db.apache.org/derby/docs/10.2/ref/rrefschemaname.html.
My take is that this is expected behavior for Derby. How did you
create the database tables? The tables might have been created under
the default schema, APP. If that's the case you might not need the
username and password properties at all (Derby doesn't require them by
default).
-Mike
On Nov 1, 2007 9:23 AM, Gul Onural <onural@nortel.com> wrote:
>
> What would be the cause of the following exception ? I am not sure where
> the 'ADMIN' schema come from ?
>
> In my persistence.xml I specify admin as a user name and password, is
> there something wrong there ? If I change the user name to be foo, I get
> the same exception with 'FOO' instead of 'ADMIN :
>
> <properties>
> <property name="openjpa.ConnectionURL"
> value="jdbc:derby:testdb;create=true;user=admin;password=admin"/>
> <property name="openjpa.ConnectionDriverName"
> value="org.apache.derby.jdbc.EmbeddedDriver"/>
> <property name="openjpa.ConnectionUserName"
> value="admin"/>
> <property name="openjpa.ConnectionPassword"
> value="admin"/>
> </properties>
>
> Any help will be really appriciated.
>
> Thanks,
>
> Gul
>
>
>
> [11/1/07 9:09:21:192 GMT-05:00] 00000024 SystemErr R ... 9
> more
> [11/1/07 9:09:21:192 GMT-05:00] 00000024 SystemErr R Caused by:
> org.apache.openjpa.lib.jdbc.ReportingSQLException: Schema 'ADMIN' does
> not exist {INSERT INTO MYTABLE(name, lastname) VALUES (?, ?)}
> [code=20000, state=42Y07]
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConne
> ctionDecorator.java:200)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$000(Loggin
> gConnectionDecorator.java:56)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection
> .prepareStatement(LoggingConnectionDecorator.java:227)
> at
> org.apache.openjpa.lib.jdbc.DelegatingConnection.prepareStatement(Delega
> tingConnection.java:163)
> at
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringCo
> nnection.prepareStatement(ConfiguringConnectionDecorator.java:140)
> at
> org.apache.openjpa.lib.jdbc.DelegatingConnection.prepareStatement(Delega
> tingConnection.java:163)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager$RefCountConnection.prepa
> reStatement(JDBCStoreManager.java:1308)
> at
> org.apache.openjpa.lib.jdbc.DelegatingConnection.prepareStatement(Delega
> tingConnection.java:152)
> at
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInterna
> l(PreparedStatementManagerImpl.java:90)
> at
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(Prepar
> edStatementManagerImpl.java:71)
> at
> org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flushPrimaryR
> ow(OperationOrderUpdateManager.java:203)
> at
> org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flush(Operati
> onOrderUpdateManager.java:89)
> at
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdat
> eManager.java:89)
> at
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdat
> eManager.java:72)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.j
> ava:514)
> at
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreMa
> nager.java:130)
> at
> org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1965)
> at
> org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1863)
> at
> org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:17
> 81)
> at
> org.apache.openjpa.kernel.LocalManagedRuntime.commit(LocalManagedRuntime
> .java:80)
> at
> org.apache.openjpa.kernel.BrokerImpl.commit(BrokerImpl.java:1311)
> at
> org.apache.openjpa.kernel.DelegatingBroker.commit(DelegatingBroker.java:
> 866)
> at
> org.apache.openjpa.persistence.EntityManagerImpl.commit(EntityManagerImp
> l.java:409)
>
>
|