>>>>> "JTA" == Jean T Anderson <[EMAIL PROTECTED]> writes:
JTA> Does this FAQ help?
JTA> http://incubator.apache.org/derby/faq.html#schema_exist
This does not handle the same issue as reported in DERBY-230.
As the subject says, DERBY-230 reports that it is possible to get the
exception "Schema already exists" when creating a table.
The FAQ addresses the issue I raised last week about getting "Schema
does not exist" when trying to access a non-existing table in the
default schema if the default schema has not been created. I still
think the most intuitive would be to get "Table does not exist" in
this case.
However, I do not think this currently is a very big problem. As long
as Derby lacks support for GRANT/REVOKE, I guess the only reason for
using a specific user is to get a specific default schema. Hence, I
would guess that people that connect as a specific user probably knows
about how the default schema is determined.
The reason I stumbled over this problem was that I modified the demo
application SimpleApp which connects as User1. A mistake when
modifying this program resulted in "Schema User1 does not exist" which
was very confusing to me since at that time I did not know how the
default schema was determined. I think SimpleApp should be modified
to not connect as a specific user. In my opinion that would reduce
the potential for confusion among new Derby programmers.
--
�ystein
