Thanks for the hint, the schema is app. It seems that when I use ij (EmbeddedMode) to connect to jdbc:derby:realty;(create=true) and use hibernate, it creates/connects the database in two different physical location. When I use ij, the database folder is created under C:\server\javadb10.3.1.4\bin, but when I use Hibernate, it must be somewhere else, at least I cannot find it under C:\server\javadb10.3.1.4\bin.
But now I found a solution, using the Server Mode instead of the Embedded Mode, which somehow makes sure that I'm using the same (physical) database. <property name="driverClass"><value>org.apache.derby.jdbc.ClientDriver</value></property> <property name="jdbcUrl"><value>jdbc:derby://localhost:1527/realty;create=true</value></property> Dyre.Tjeldvoll wrote: > > > select t.tablename, s.schemaname from sys.systables t, sys.sysschemas s > where t.tablename = 'USERDATA' and t.schemaid = s.schemaid; > > This should also tell you if you have multiple copies of USERDATA in > different schemas. > > -- View this message in context: http://www.nabble.com/Hibernate%3A-table-view-does-not-exist-tf4521125.html#a12913106 Sent from the Apache Derby Users mailing list archive at Nabble.com.
