malesch <[email protected]> writes: > I am seeing some very strange behavior with my Derby DB > (version 10.4.2.0 and 10.5.3.0). > > If I load my DB from a JAR file, I am missing some table > entries, that are existing if I extract the DB from the > same JAR file and load it from the file system. > > How can I understand this behavior, is there an > explanation for this?
That seems weird. Are you connecting with the same user name (or none) in the two scenarios? Occasionally we see users miss some tables because they end up in an unexpected schema; the default schema is the user name (or "APP" if not provided). If this is not the issue, are you able to provide a repro for it? Thanks, Dag
