Dag H. Wanvik wrote:
Thanks for trying this out, Stan! I really appreciate it.
Stanley Bradbury <[EMAIL PROTECTED]> writes:
======== SNIP =======
Making APP a valid user did not work for me either. Prior to version
10.2 I am not aware of there being a DBO but I understand the system
tables were owned by DBA so I created such a user and it appears to
have worked but since there is no schema called DBA any SQL causes
errors. Is there anyway for an end-user to tell whom the code expects
the DBO to be?
Not sure, I guess
select AUTHORIZATIONID from sys.sysschemas where schemaname = 'SYS';
would not be permissible unless necessary permissions were granted?
C:\Stan\L3\10.3\DBO>java org.apache.derby.tools.ij
ij version 10.3
ij> connect 'jdbc:derby:noUserDB;upgrade=true;user=DBA;password=DBA';
ij> select columnnumber, columnname from sys.syscolumns where
referenceid in (select tableid from sys.systables where ta
blename = 'SYSTABLES') order by columnnumber;
ERROR 42Y07: Schema 'DBA' does not exist
I tried to recreate this, but I could not. Can you show me exactly how
you did this? Please also see my reply to Dan's mail; I did some more
experiments.
Thanks,
Dag
ij> set schema app;
0 rows inserted/updated/deleted
ij> select columnnumber, columnname from sys.syscolumns where
referenceid in (select tableid from sys.systables where tablename =
SYSTABLES') order by columnnumber;
COLUMNNUMB&|COLUMNNAME
------------------------------------------------------------------------------------------------------------------------
--------------------
1 |TABLEID
2 |TABLENAME
3 |TABLETYPE
4 |SCHEMAID
5 |LOCKGRANULARITY
5 rows selected
ij> exit;
%%% Attempts w/APP %%%%%%%%%%%
ij version 10.3
ij> connect 'jdbc:derby:tstDB;upgrade=true;user=APP;password=APP';
ERROR 08004: User 'APP' cannot hard upgrade database 'tstDB'. Only the
database owner can perform this operation.
It would be nice as this all gets hammered out if the upgrade tests were
enhanced to test these cases. I don't know how hard that might be as
the current framework may need to be enhanced - there may be a need to
test multiple different databases - not sure. If anyone looks at this
and can't get the tests to work it probably is worth a JIRA to doc the
issues with the test and hopefully get the test cases in, in the future.
