When you connect as user foo, Java DB sets the default schema to FOO. However,
that schema doesn't exist yet, so you connect to the APP schema -- or any other
one. When you create a table specifying an unqualified table name, that table is
created in the default schema (which gets created at that point). So you get a
table named FOO.PERSON, but the DB Explorer shows the tables in the APP schema.

I don't see what could DB Explorer do here, it looks more like an user error to
me. IIRC this is the reason the user name of the sample database is app. Also
note that you don't encounter this issue if you create the database using Tools
- Java DB Database - Create Database. Suggest closing as invalid.

BTW please do not use "current" as the version, use whichever version you
encountered the issue in or the version currently in development (6.0). Also
note db/dbschema is for dbschema issues only, but dbschema is not used in DB
Explorer.

I don't understand how we could call this "user error" when it is just a basic
thing that anyone would do.  We are here to make life easier for the user, not
to expect them to know the intricacies of Derby schema management.  As you can
see on the nbusers thread that initiated this bug, it caused a lot of confusion
for both the user and myself (as a newbie to the DB explorer).

I think it's a bit of silliness that Derby would log you in to a schema that
doesn't exist.  But we have to deal with that and try to be as helpful as we can.

I don't see how it can be seen as reasonable for DB explorer to display the APP
schema when the user currently logged in has 'FOO' as their default schema.  At
a minimum DB explorer should show the tables for the default schema of the user.
 Better yet, it should show tables for all the schemas (with a possible ability
to let the user filter out certain schemas they don't care about).

Finally, I don't think we should expect all users to create tables using our
wizard in order to see their tables in the explorer.  Many many users have and
maintain SQL scripts to create tables.

This bug should NOT be closed as invalid unless we can reach some kind of
consensus here.  So far I am not convinced.

I changed the version, sorry about that.  

Subcomponents continue to baffle me.  Saying that explorer doesn't use dbschema
to obtain the schema is un-obvious.  I was also told that 'databinding' is an
invalid component for issues around binding databases to visual components. 
This all reminds me of a scene in a Jack Aubrey novel where all the sailors are
laughing at a landlubber saying 'oi, this guy thought that there should be guns
on the gun deck.  har har har!"

Yes, displaying all schemas is something we should consider, other tools do it.
I wondered why we don't do it the first time I saw the DB Explorer, but I guess
I just got used to it. Anyway, seems you have some ideas on how to address this.

Showing other schemas sounds like a fairly hefty UI change, I'm thinking this probably can't go in after feature freeze.
 Any other opinions on this?

Switching to enhancement for the following reasons.

> I don't see how it can be seen as reasonable for DB explorer to display the
> APP schema when the user currently logged in has 'FOO' as their default
> schema.

The user chooses the schema when registering the connection. In this case the user chose the APP schema, so that's what
the DB Explorer displays.  

> At a minimum DB explorer should show the tables for the default schema of the
> user.

Agreed, but it's not that trivial, probably not doable at all without a Connection.getDefaultSchema() method. I recall
sending Lance a mail about it some time ago.

> Finally, I don't think we should expect all users to create tables using our
> wizard in order to see their tables in the explorer.

I didn't suggest that. I said that you didn't encounter the issue if you used the NB support to create the *database*,
not the tables.

Switching to enhancement - show all schemas 

Reassigned to new owner.